Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57bc34ae6c4d099e68c3862ba116e15ffd9a50e881451d698a01de678fa53dd3

Tx prefix hash: 5b388b41fa26f10f7284a667b322d8c8a757cad5c62ff25a48e0bda96766e77a
Tx public key: 32891933a587fee8eb236d5e4223743d1ab98a3e0d08fbee682cae361a6c31bf
Timestamp: 1714228614 Timestamp [UCT]: 2024-04-27 14:36:54 Age [y:d:h:m:s]: 00:343:20:09:22
Block: 1009706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245799 RingCT/type: yes/0
Extra: 0132891933a587fee8eb236d5e4223743d1ab98a3e0d08fbee682cae361a6c31bf02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ab6f31a4c2368bdac8fa16b0a2f108d68f38120edb1f55d91cb97a25931f4b7 0.600000000000 1471454 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": 1009716, "vin": [ { "gen": { "height": 1009706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ab6f31a4c2368bdac8fa16b0a2f108d68f38120edb1f55d91cb97a25931f4b7" } } ], "extra": [ 1, 50, 137, 25, 51, 165, 135, 254, 232, 235, 35, 109, 94, 66, 35, 116, 61, 26, 185, 138, 62, 13, 8, 251, 238, 104, 44, 174, 54, 26, 108, 49, 191, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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