Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79a34549c60af580fea81c66efce3bd132724b32c0f905d7d4ec21241328222c

Tx prefix hash: 7ce8a78a5b9187ac1b339c6fa0dfba65fdcbe907cc8c80e936df1fd47327a028
Tx public key: d6565bf74c05db7dd0705786893884e5c028dab206befbba67b525f8a38dab6a
Timestamp: 1714610249 Timestamp [UCT]: 2024-05-02 00:37:29 Age [y:d:h:m:s]: 00:317:22:46:18
Block: 1012877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227298 RingCT/type: yes/0
Extra: 01d6565bf74c05db7dd0705786893884e5c028dab206befbba67b525f8a38dab6a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50aed0e4a878d2a2ccddae5ec6d269d17d2db91effd41066c7c2bbd93c66df9b 0.600000000000 1475534 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": 1012887, "vin": [ { "gen": { "height": 1012877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50aed0e4a878d2a2ccddae5ec6d269d17d2db91effd41066c7c2bbd93c66df9b" } } ], "extra": [ 1, 214, 86, 91, 247, 76, 5, 219, 125, 208, 112, 87, 134, 137, 56, 132, 229, 192, 40, 218, 178, 6, 190, 251, 186, 103, 181, 37, 248, 163, 141, 171, 106, 2, 17, 0, 0, 0, 2, 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