Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06b2f542f58c756f3ae5ee41f3947455983f2134f56d0b442946e2e11e535431

Tx prefix hash: 1ec9df000879c44c7c118c7b7d74f5b12a2c91566752c7ba411167aaf3dc7d0d
Tx public key: acdbd3e9ff06f7562816939f1267e2c245dbf8c86b3b09d3c320848fbb47e8a5
Timestamp: 1717268868 Timestamp [UCT]: 2024-06-01 19:07:48 Age [y:d:h:m:s]: 01:221:00:59:31
Block: 1034923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416643 RingCT/type: yes/0
Extra: 01acdbd3e9ff06f7562816939f1267e2c245dbf8c86b3b09d3c320848fbb47e8a50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c2e9a6d8b72c2e85c94a4f0204c1729f19b9df7db6955424986fbbb7197fc77 0.600000000000 1503442 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": 1034933, "vin": [ { "gen": { "height": 1034923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2e9a6d8b72c2e85c94a4f0204c1729f19b9df7db6955424986fbbb7197fc77" } } ], "extra": [ 1, 172, 219, 211, 233, 255, 6, 247, 86, 40, 22, 147, 159, 18, 103, 226, 194, 69, 219, 248, 200, 107, 59, 9, 211, 195, 32, 132, 143, 187, 71, 232, 165, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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