Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ac0d6cfddd636fadcade6bfa9607f7a99ad94a1f89fc6327d8c19ff8a6d6769

Tx prefix hash: f0344b1b9b4ee1f64c23bfb3fc8799b18003eaa7c6ef627abf430d02a8ffb136
Tx public key: 098bf4dbfbcfeeefe05ac7975ee3b6c177f0aad7fa5dc05900f0495e5606aa9e
Timestamp: 1749006755 Timestamp [UCT]: 2025-06-04 03:12:35 Age [y:d:h:m:s]: 00:159:22:00:52
Block: 1297494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111959 RingCT/type: yes/0
Extra: 01098bf4dbfbcfeeefe05ac7975ee3b6c177f0aad7fa5dc05900f0495e5606aa9e02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b26c66c2aaebe65b08ff2e8fc1ec7fcfef003dbdde1b4bfeed287b843b35fd3 0.600000000000 1785013 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": 1297504, "vin": [ { "gen": { "height": 1297494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b26c66c2aaebe65b08ff2e8fc1ec7fcfef003dbdde1b4bfeed287b843b35fd3" } } ], "extra": [ 1, 9, 139, 244, 219, 251, 207, 238, 239, 224, 90, 199, 151, 94, 227, 182, 193, 119, 240, 170, 215, 250, 93, 192, 89, 0, 240, 73, 94, 86, 6, 170, 158, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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