Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5227d1175245dc8894cf4bb4e821592b8c1c37d4ab7da725ff5589efe6f23e4d

Tx prefix hash: e553c3542855106dd23b09f7ca5dca397b157ae92fcd6cc6d3eb4b27d1219ffa
Tx public key: 1c9cd324066e8df55245c82c15f12091ababb9bc98ff8f9be3dbe3f35df25c51
Timestamp: 1742315682 Timestamp [UCT]: 2025-03-18 16:34:42 Age [y:d:h:m:s]: 00:295:06:02:03
Block: 1242103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208808 RingCT/type: yes/0
Extra: 011c9cd324066e8df55245c82c15f12091ababb9bc98ff8f9be3dbe3f35df25c510211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa9e2c6dcde775a71673fd1ba61eeb9189c64addb8a98fd810a83f5c9de68d3e 0.600000000000 1729076 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": 1242113, "vin": [ { "gen": { "height": 1242103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa9e2c6dcde775a71673fd1ba61eeb9189c64addb8a98fd810a83f5c9de68d3e" } } ], "extra": [ 1, 28, 156, 211, 36, 6, 110, 141, 245, 82, 69, 200, 44, 21, 241, 32, 145, 171, 171, 185, 188, 152, 255, 143, 155, 227, 219, 227, 243, 93, 242, 92, 81, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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