Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 230177fc6cdd443e2a1ffb70b39a193f37ce61bc2323470265553437b71ba24b

Tx prefix hash: 6d24005159f0b54c9a934e53fd352501a225fe2ef282e2f21c4af76dce053b6e
Tx public key: 293e864d709bb7f65b81fd58b729e54c2e9b419975c2ddd9319e7144b7ef3259
Timestamp: 1728072784 Timestamp [UCT]: 2024-10-04 20:13:04 Age [y:d:h:m:s]: 00:050:22:30:43
Block: 1124482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36389 RingCT/type: yes/0
Extra: 01293e864d709bb7f65b81fd58b729e54c2e9b419975c2ddd9319e7144b7ef3259021100000005e914dd15000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: 66fc8b10b732d3e612e4a9568d4d787950d765382519508723fd0966fa21b3e0 0.600200000000 1607109 of 0

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": 1124492, "vin": [ { "gen": { "height": 1124482 } } ], "vout": [ { "amount": 600200000, "target": { "key": "66fc8b10b732d3e612e4a9568d4d787950d765382519508723fd0966fa21b3e0" } } ], "extra": [ 1, 41, 62, 134, 77, 112, 155, 183, 246, 91, 129, 253, 88, 183, 41, 229, 76, 46, 155, 65, 153, 117, 194, 221, 217, 49, 158, 113, 68, 183, 239, 50, 89, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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