Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3efdbf42e1f8035e0be30d700837ac9b640e60b0abc06ec860c0e5ab72be5ceb

Tx prefix hash: 04f315d0af1ad4566718a30c249f55195ed68678f79e6caa86268e46baf33766
Tx public key: eb6cc15565d2ff0fe82febe9caf8697f4fb00a625a423bdd3c054d9b502350b3
Timestamp: 1763777000 Timestamp [UCT]: 2025-11-22 02:03:20 Age [y:d:h:m:s]: 00:037:10:42:00
Block: 1417349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26824 RingCT/type: yes/0
Extra: 01eb6cc15565d2ff0fe82febe9caf8697f4fb00a625a423bdd3c054d9b502350b302110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9b023e388515803f33f7baae67befebb79400651e9714ebdd3fbb3a7e75b7b6 0.600000000000 1905872 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": 1417359, "vin": [ { "gen": { "height": 1417349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9b023e388515803f33f7baae67befebb79400651e9714ebdd3fbb3a7e75b7b6" } } ], "extra": [ 1, 235, 108, 193, 85, 101, 210, 255, 15, 232, 47, 235, 233, 202, 248, 105, 127, 79, 176, 10, 98, 90, 66, 59, 221, 60, 5, 77, 155, 80, 35, 80, 179, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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