Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7ae3ddb75b338674d9a329beb63b4c8ac5d10b1cafb30da245529b4001fd447

Tx prefix hash: 4095a94ae0e7783e5e2ef04a3bbda57a258f25c6476152cec5b9cf5f8cd76c61
Tx public key: e2ebbe55227a3c6557a1887855f2d948507dbfef37272dfaedd445c237e07f0c
Timestamp: 1728551784 Timestamp [UCT]: 2024-10-10 09:16:24 Age [y:d:h:m:s]: 00:105:15:27:20
Block: 1128455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75481 RingCT/type: yes/0
Extra: 01e2ebbe55227a3c6557a1887855f2d948507dbfef37272dfaedd445c237e07f0c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b419b7c91d7879cfe033f1ac394434d06b2d46c9fdfe4e173abe172f534e9e16 0.600000000000 1611274 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": 1128465, "vin": [ { "gen": { "height": 1128455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b419b7c91d7879cfe033f1ac394434d06b2d46c9fdfe4e173abe172f534e9e16" } } ], "extra": [ 1, 226, 235, 190, 85, 34, 122, 60, 101, 87, 161, 136, 120, 85, 242, 217, 72, 80, 125, 191, 239, 55, 39, 45, 250, 237, 212, 69, 194, 55, 224, 127, 12, 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