Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e624dbd9e081ce607526521d07951a07b2b5f1d9a0c3c10fdd66e58be24453

Tx prefix hash: 348d0fa9bb5fabe60e8caa974f27b57134206532927f3322ad68a13d990ec64b
Tx public key: 5a64dea3cf7cb867a87793625cf68a5f10320c41fd0bb97a2a0237162e791b2e
Timestamp: 1737718953 Timestamp [UCT]: 2025-01-24 11:42:33 Age [y:d:h:m:s]: 00:144:04:37:28
Block: 1204261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102799 RingCT/type: yes/0
Extra: 015a64dea3cf7cb867a87793625cf68a5f10320c41fd0bb97a2a0237162e791b2e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 638a1853e5f43fff67df73f16c65dd8193ebb35d39931613c62b610e9f870702 0.600000000000 1690946 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": 1204271, "vin": [ { "gen": { "height": 1204261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "638a1853e5f43fff67df73f16c65dd8193ebb35d39931613c62b610e9f870702" } } ], "extra": [ 1, 90, 100, 222, 163, 207, 124, 184, 103, 168, 119, 147, 98, 92, 246, 138, 95, 16, 50, 12, 65, 253, 11, 185, 122, 42, 2, 55, 22, 46, 121, 27, 46, 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