Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ceab953769cf80773f7fe1806e5c3bc35c3c4f9c665285921f52e40f90bce4

Tx prefix hash: 5e08d60d5e919ed91a1f737275b20f56955f8ed390d208721905bce64cb1652d
Tx public key: 8200ca67f56bab09cacc2bf6799c25a238baaff3e7f5a3f3491e74abc39c8385
Timestamp: 1723581269 Timestamp [UCT]: 2024-08-13 20:34:29 Age [y:d:h:m:s]: 00:307:09:13:02
Block: 1087246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219503 RingCT/type: yes/0
Extra: 018200ca67f56bab09cacc2bf6799c25a238baaff3e7f5a3f3491e74abc39c8385021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e35e64e6cd4831bd719069c3f601fe1cc8c5ec5c309fdf3bb09d44b44705038 0.600000000000 1561853 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": 1087256, "vin": [ { "gen": { "height": 1087246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e35e64e6cd4831bd719069c3f601fe1cc8c5ec5c309fdf3bb09d44b44705038" } } ], "extra": [ 1, 130, 0, 202, 103, 245, 107, 171, 9, 202, 204, 43, 246, 121, 156, 37, 162, 56, 186, 175, 243, 231, 245, 163, 243, 73, 30, 116, 171, 195, 156, 131, 133, 2, 17, 0, 0, 0, 6, 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