Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ec5735f9101e0d0a7d92070c1dca71c5c8035228ac991b2397ac4e841b7607

Tx prefix hash: bdcf00d8feb4603d3216ba9e7dbdd9f68a2f558afb272f3b546970265d6b30c1
Tx public key: f3b371fbd12f2064d057a3f32168c0c0d684817bded16c34b90f6459face4c23
Timestamp: 1720010707 Timestamp [UCT]: 2024-07-03 12:45:07 Age [y:d:h:m:s]: 00:274:13:19:27
Block: 1057646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196159 RingCT/type: yes/0
Extra: 01f3b371fbd12f2064d057a3f32168c0c0d684817bded16c34b90f6459face4c230211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c1cd0cf1ab128968b9e67af0de8435e9c5b03b2bc94ac8d456baf882d9c8ee0 0.600000000000 1528083 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": 1057656, "vin": [ { "gen": { "height": 1057646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c1cd0cf1ab128968b9e67af0de8435e9c5b03b2bc94ac8d456baf882d9c8ee0" } } ], "extra": [ 1, 243, 179, 113, 251, 209, 47, 32, 100, 208, 87, 163, 243, 33, 104, 192, 192, 214, 132, 129, 123, 222, 209, 108, 52, 185, 15, 100, 89, 250, 206, 76, 35, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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