Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31768e1ab5590b5b24b105dc8a210aed8892e04e6b3c410347cf9a75f456a6e0

Tx prefix hash: 0a051a61882958c382d2f19efd73dbec83db7e0f7849d85db7031cfcd35f900b
Tx public key: 83b9b64961276564442a01f95ebfd24765628d0ae905fe4e10fdf28571a47301
Timestamp: 1714408072 Timestamp [UCT]: 2024-04-29 16:27:52 Age [y:d:h:m:s]: 00:339:19:36:12
Block: 1011193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242919 RingCT/type: yes/0
Extra: 0183b9b64961276564442a01f95ebfd24765628d0ae905fe4e10fdf28571a473010211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.617650000000 dcy

stealth address amount amount idx
00: d4b86899e0052e51a9dd74e051ee557ee266dfbef9a5c8caca7a7139d89f5c11 0.617650000000 1473357 of 0

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": 1011203, "vin": [ { "gen": { "height": 1011193 } } ], "vout": [ { "amount": 617650000, "target": { "key": "d4b86899e0052e51a9dd74e051ee557ee266dfbef9a5c8caca7a7139d89f5c11" } } ], "extra": [ 1, 131, 185, 182, 73, 97, 39, 101, 100, 68, 42, 1, 249, 94, 191, 210, 71, 101, 98, 141, 10, 233, 5, 254, 78, 16, 253, 242, 133, 113, 164, 115, 1, 2, 17, 0, 0, 0, 3, 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