Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b98e3ad07be764c61c84c1b928580ba05f6db3dbe4fcee02a9ccd90698a68cd

Tx prefix hash: b8a247628494d1deae0d3c396eb82d0ad37bfaff465f2a008354563424380c35
Tx public key: 6df830e8b8913ce43fd18f14d16123c8dd2979b58ef67df4ca803e548b909625
Timestamp: 1729965554 Timestamp [UCT]: 2024-10-26 17:59:14 Age [y:d:h:m:s]: 00:165:13:24:02
Block: 1140148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118120 RingCT/type: yes/0
Extra: 016df830e8b8913ce43fd18f14d16123c8dd2979b58ef67df4ca803e548b9096250211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3ec0dfa29dfe1f3d9ab1d2b807bb1fbe3a22dcd5aa78fa79f95d0430b87000 0.600000000000 1623943 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": 1140158, "vin": [ { "gen": { "height": 1140148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3ec0dfa29dfe1f3d9ab1d2b807bb1fbe3a22dcd5aa78fa79f95d0430b87000" } } ], "extra": [ 1, 109, 248, 48, 232, 184, 145, 60, 228, 63, 209, 143, 20, 209, 97, 35, 200, 221, 41, 121, 181, 142, 246, 125, 244, 202, 128, 62, 84, 139, 144, 150, 37, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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