Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86309c179db6b02f073972394d80585eba662985a4316004c3bdfd6cce1c0a29

Tx prefix hash: e12df3a974d76b47a2461b6da750b6c5d8c6902b5aed917085c61120c444803e
Tx public key: a218101215b811f2ca9ef1b1570f0105c902e338f7e452b12d9b98fcc24bad98
Timestamp: 1705614788 Timestamp [UCT]: 2024-01-18 21:53:08 Age [y:d:h:m:s]: 01:297:02:50:42
Block: 938274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471172 RingCT/type: yes/0
Extra: 01a218101215b811f2ca9ef1b1570f0105c902e338f7e452b12d9b98fcc24bad9802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6af7e222dcd6a92c9028b8e727b1e82246e2ed0a77c276a64063942235d9be7 0.600000000000 1396344 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": 938284, "vin": [ { "gen": { "height": 938274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6af7e222dcd6a92c9028b8e727b1e82246e2ed0a77c276a64063942235d9be7" } } ], "extra": [ 1, 162, 24, 16, 18, 21, 184, 17, 242, 202, 158, 241, 177, 87, 15, 1, 5, 201, 2, 227, 56, 247, 228, 82, 177, 45, 155, 152, 252, 194, 75, 173, 152, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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