Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f935dbe2def482043d294443be5f08bf3ab21121792ca14d72d2fcd0f89553

Tx prefix hash: 9f707ac97ee72d300a60380c10a7a5a2adbd122c37389c3b99ec3d40f72b713c
Tx public key: 9e686048791f0c66dae1e9c3bc10572cb76bb1b2d81b0d0774bf6eeae0325088
Timestamp: 1714666075 Timestamp [UCT]: 2024-05-02 16:07:55 Age [y:d:h:m:s]: 01:189:06:05:29
Block: 1013337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393890 RingCT/type: yes/0
Extra: 019e686048791f0c66dae1e9c3bc10572cb76bb1b2d81b0d0774bf6eeae03250880211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30f54f0622890c3530dffb1113f8bae84783a767175bc30215cc7a334b49f8e 0.600000000000 1476128 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": 1013347, "vin": [ { "gen": { "height": 1013337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30f54f0622890c3530dffb1113f8bae84783a767175bc30215cc7a334b49f8e" } } ], "extra": [ 1, 158, 104, 96, 72, 121, 31, 12, 102, 218, 225, 233, 195, 188, 16, 87, 44, 183, 107, 177, 178, 216, 27, 13, 7, 116, 191, 110, 234, 224, 50, 80, 136, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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