Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e935ef07a8a0391ef7d6fbd5994cff5a0e0f601955b4b591d5586ef47df4e7b

Tx prefix hash: 93e6c30d645a60223c97885a3eba694543a6affc47e8b19d1f9184f77fe161e8
Tx public key: 2ac2c961606ba000cfcae564466bbec0c44688fcc06d7750e9ca5ba570a070e0
Timestamp: 1712121782 Timestamp [UCT]: 2024-04-03 05:23:02 Age [y:d:h:m:s]: 01:071:22:56:06
Block: 992209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312378 RingCT/type: yes/0
Extra: 012ac2c961606ba000cfcae564466bbec0c44688fcc06d7750e9ca5ba570a070e00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86384aa2a2aae98aad3c72d10c3039a4bb074b776a12d2faf8a177e9de7f979a 0.600000000000 1452549 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": 992219, "vin": [ { "gen": { "height": 992209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86384aa2a2aae98aad3c72d10c3039a4bb074b776a12d2faf8a177e9de7f979a" } } ], "extra": [ 1, 42, 194, 201, 97, 96, 107, 160, 0, 207, 202, 229, 100, 70, 107, 190, 192, 196, 70, 136, 252, 192, 109, 119, 80, 233, 202, 91, 165, 112, 160, 112, 224, 2, 17, 0, 0, 0, 4, 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