Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd932f57805f9c35f59068fcca11b58dc88ce0a9e5bc3350d17e5bfaabaec513

Tx prefix hash: e0d97dbe07fbd4f52a611947e221c6e12e3bdce344b6507dde346f639b78a943
Tx public key: f3b6bbb5c3d22f09341e0a1ec33383bc610d2d2baddcf166d51803b230cbb70f
Timestamp: 1730315882 Timestamp [UCT]: 2024-10-30 19:18:02 Age [y:d:h:m:s]: 00:160:20:55:33
Block: 1143007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114801 RingCT/type: yes/0
Extra: 01f3b6bbb5c3d22f09341e0a1ec33383bc610d2d2baddcf166d51803b230cbb70f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4440352c58d5c36326a6497b3aeb142cfddc17990e000c0be71b2cd3e314dfed 0.600000000000 1626864 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": 1143017, "vin": [ { "gen": { "height": 1143007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4440352c58d5c36326a6497b3aeb142cfddc17990e000c0be71b2cd3e314dfed" } } ], "extra": [ 1, 243, 182, 187, 181, 195, 210, 47, 9, 52, 30, 10, 30, 195, 51, 131, 188, 97, 13, 45, 43, 173, 220, 241, 102, 213, 24, 3, 178, 48, 203, 183, 15, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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