Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 298bd2ec12294761d35bbe783c4f61e6d7a4ff2c78584b8ad4ee95ea7bdacac3

Tx prefix hash: 17c5170c255850d7807ad1cd56bc5660b3339e8487430b2365ce2271c521d8eb
Tx public key: 00e0e97d1192b98e5671cb3dc7bd551bef91151e9168613dac6cb4ef2db5a444
Timestamp: 1720627388 Timestamp [UCT]: 2024-07-10 16:03:08 Age [y:d:h:m:s]: 00:269:08:57:43
Block: 1062762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192443 RingCT/type: yes/0
Extra: 0100e0e97d1192b98e5671cb3dc7bd551bef91151e9168613dac6cb4ef2db5a44402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff186c26717114ff0e1e2107a202f36fe3cb2b88e3b59e5cb5e76a95782b88f0 0.600000000000 1533269 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": 1062772, "vin": [ { "gen": { "height": 1062762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff186c26717114ff0e1e2107a202f36fe3cb2b88e3b59e5cb5e76a95782b88f0" } } ], "extra": [ 1, 0, 224, 233, 125, 17, 146, 185, 142, 86, 113, 203, 61, 199, 189, 85, 27, 239, 145, 21, 30, 145, 104, 97, 61, 172, 108, 180, 239, 45, 181, 164, 68, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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