Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f2b0d6856709397ec44c339f7e9a6826eef08dca839464c7ecfaf2c38fd279

Tx prefix hash: 828771026fa767623985cd742675d801ba059190c2e41e09ad8c2b810c742881
Tx public key: 302956771fe02b528da4e814e98d80984f19d3b9d061c2d611a8c3def3abdd47
Timestamp: 1707014422 Timestamp [UCT]: 2024-02-04 02:40:22 Age [y:d:h:m:s]: 00:285:01:11:20
Block: 949884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204094 RingCT/type: yes/0
Extra: 01302956771fe02b528da4e814e98d80984f19d3b9d061c2d611a8c3def3abdd470211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d80dd7a3aebc2a9d68513ace702a03bfce1f23192ef246b947802cbd5956ee14 0.600000000000 1408418 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": 949894, "vin": [ { "gen": { "height": 949884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d80dd7a3aebc2a9d68513ace702a03bfce1f23192ef246b947802cbd5956ee14" } } ], "extra": [ 1, 48, 41, 86, 119, 31, 224, 43, 82, 141, 164, 232, 20, 233, 141, 128, 152, 79, 25, 211, 185, 208, 97, 194, 214, 17, 168, 195, 222, 243, 171, 221, 71, 2, 17, 0, 0, 0, 3, 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