Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 824d64432ba1761de9d3a7471416e5d5b51a2eac7df87bbd636552292f4bcda9

Tx prefix hash: 0c58a90930c210f7e3383c0fdcfd98f4f400f569280e1638ef98817a4a5bbe64
Tx public key: ede826b8072ee511a7a37b18f5f67bfa05b920252833f4302e33a3b62f51009e
Timestamp: 1711721825 Timestamp [UCT]: 2024-03-29 14:17:05 Age [y:d:h:m:s]: 01:012:17:12:45
Block: 988942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270044 RingCT/type: yes/0
Extra: 01ede826b8072ee511a7a37b18f5f67bfa05b920252833f4302e33a3b62f51009e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 535757e87bc9a715d5c837647bf8d470ba4b572f3149bc93b04e5f26180c321e 0.600000000000 1449233 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 988952, "vin": [ { "gen": { "height": 988942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "535757e87bc9a715d5c837647bf8d470ba4b572f3149bc93b04e5f26180c321e" } } ], "extra": [ 1, 237, 232, 38, 184, 7, 46, 229, 17, 167, 163, 123, 24, 245, 246, 123, 250, 5, 185, 32, 37, 40, 51, 244, 48, 46, 51, 163, 182, 47, 81, 0, 158, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8