Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 618a3f43b07aece7833fc0bf3faa6de26c0fddaf60c1276899e898396ea98065

Tx prefix hash: e3570e95b2a864f2271363e2de44d9ea3ee1daaa364d3a767dab20997d4f6325
Tx public key: 3c0b292349e9900ebe58e5ce328d7d01ddc24c3e49df3ff954f4fbe929a31de7
Timestamp: 1620824854 Timestamp [UCT]: 2021-05-12 13:07:34 Age [y:d:h:m:s]: 03:177:18:43:04
Block: 259490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 887462 RingCT/type: yes/0
Extra: 013c0b292349e9900ebe58e5ce328d7d01ddc24c3e49df3ff954f4fbe929a31de702110000000fb1d898ff000000000000000000

1 output(s) for total of 84.762246623000 dcy

stealth address amount amount idx
00: 013d7e576e3f17c1e5e88a2a6ba6bc6138c69bce9f5a380264f8b75d65d86515 84.762246623000 546585 of 0

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": 259500, "vin": [ { "gen": { "height": 259490 } } ], "vout": [ { "amount": 84762246623, "target": { "key": "013d7e576e3f17c1e5e88a2a6ba6bc6138c69bce9f5a380264f8b75d65d86515" } } ], "extra": [ 1, 60, 11, 41, 35, 73, 233, 144, 14, 190, 88, 229, 206, 50, 141, 125, 1, 221, 194, 76, 62, 73, 223, 63, 249, 84, 244, 251, 233, 41, 163, 29, 231, 2, 17, 0, 0, 0, 15, 177, 216, 152, 255, 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