Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02845147232cfa275c58e31aa2baf85315006da62a4e30782f75b74ff8152677

Tx prefix hash: df7da2503a0fbccb71a1c7bfb1844118c745f2bd3ab2ca0bb506e972874f6229
Tx public key: 0c01b8a057669be8dd4555a4c3dde7a387ff162b20e3134907504dd9cb157cfa
Timestamp: 1752864967 Timestamp [UCT]: 2025-07-18 18:56:07 Age [y:d:h:m:s]: 00:168:16:54:30
Block: 1328309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119423 RingCT/type: yes/0
Extra: 010c01b8a057669be8dd4555a4c3dde7a387ff162b20e3134907504dd9cb157cfa021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5071f2d8ae7830447223ac7d085ce795af6c91483a3344ee0a0ebc3b3bcec3a3 0.600000000000 1816070 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": 1328319, "vin": [ { "gen": { "height": 1328309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5071f2d8ae7830447223ac7d085ce795af6c91483a3344ee0a0ebc3b3bcec3a3" } } ], "extra": [ 1, 12, 1, 184, 160, 87, 102, 155, 232, 221, 69, 85, 164, 195, 221, 231, 163, 135, 255, 22, 43, 32, 227, 19, 73, 7, 80, 77, 217, 203, 21, 124, 250, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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