Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 094411d4cc124ccbf424b4ebfedd68cb6e3d69164330e05f2d52604b4597039f

Tx prefix hash: 3cdddfd33f4869d43304ee7e3d523d8df6dcd09e3cd372327c8cf71c96f73fcb
Tx public key: e8843cb4fa74353ba2e97abf9c13e8893b8013747ed9d3d20e32fa54e2f96105
Timestamp: 1721121549 Timestamp [UCT]: 2024-07-16 09:19:09 Age [y:d:h:m:s]: 00:289:20:26:03
Block: 1066867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207080 RingCT/type: yes/0
Extra: 01e8843cb4fa74353ba2e97abf9c13e8893b8013747ed9d3d20e32fa54e2f96105021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c50b574e299afb902681efe8513b1c08ba7a20f2ef35696b3b94f2f9ff1ec3f4 0.600000000000 1537540 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": 1066877, "vin": [ { "gen": { "height": 1066867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c50b574e299afb902681efe8513b1c08ba7a20f2ef35696b3b94f2f9ff1ec3f4" } } ], "extra": [ 1, 232, 132, 60, 180, 250, 116, 53, 59, 162, 233, 122, 191, 156, 19, 232, 137, 59, 128, 19, 116, 126, 217, 211, 210, 14, 50, 250, 84, 226, 249, 97, 5, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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