Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78573b5ebdc426d539d7f0b4c8f9a1def4752d5dfd82bc98ee49fd9ad4632b24

Tx prefix hash: 56a141b2b68d0ac14c0ceb12e569a39c730489b962cb882404adad83df904614
Tx public key: 44fdec635881e0be192b937b87da2574a082efc0c06fce11374d8a16d61f6c49
Timestamp: 1747235825 Timestamp [UCT]: 2025-05-14 15:17:05 Age [y:d:h:m:s]: 00:147:21:45:02
Block: 1282835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103340 RingCT/type: yes/0
Extra: 0144fdec635881e0be192b937b87da2574a082efc0c06fce11374d8a16d61f6c4902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538102d34029d7bb7973e23ba71b8ca7c197305dc93d1a7a178a0270eba7f156 0.600000000000 1770248 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": 1282845, "vin": [ { "gen": { "height": 1282835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538102d34029d7bb7973e23ba71b8ca7c197305dc93d1a7a178a0270eba7f156" } } ], "extra": [ 1, 68, 253, 236, 99, 88, 129, 224, 190, 25, 43, 147, 123, 135, 218, 37, 116, 160, 130, 239, 192, 192, 111, 206, 17, 55, 77, 138, 22, 214, 31, 108, 73, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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