Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3290cd0b3f7eb28f4ce5c4353a18efc2dc6804cf6ee11e09756972498e240ba5

Tx prefix hash: f374f3b29c72f9c3000445066bf4c07b0494b516a9ca7fca8ebbf1f88a349485
Tx public key: edd227ebc4bf931c64e34915b9d46528758e027c1d1013b2dd365ae0dfc52c5e
Timestamp: 1704107475 Timestamp [UCT]: 2024-01-01 11:11:15 Age [y:d:h:m:s]: 01:098:01:04:54
Block: 925787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331179 RingCT/type: yes/0
Extra: 01edd227ebc4bf931c64e34915b9d46528758e027c1d1013b2dd365ae0dfc52c5e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b03df1ddb91e6d3e662155179b556171e7a0c198fcfd1f3779882002a0adcb6 0.600000000000 1383555 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": 925797, "vin": [ { "gen": { "height": 925787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b03df1ddb91e6d3e662155179b556171e7a0c198fcfd1f3779882002a0adcb6" } } ], "extra": [ 1, 237, 210, 39, 235, 196, 191, 147, 28, 100, 227, 73, 21, 185, 212, 101, 40, 117, 142, 2, 124, 29, 16, 19, 178, 221, 54, 90, 224, 223, 197, 44, 94, 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