Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd77fb47270df077b011e31239feb490aed44a8817f24c478aa36cebcbbf13ba

Tx prefix hash: 88f369513a128742f35a5f58ceb003aced72cd3da7677c73bbe0ac22300eb06e
Tx public key: 010b11b1bcab66cab8f3e4b70c5e46123d04c02bd365d0c6ec8c31e6a0ee2e46
Timestamp: 1725964053 Timestamp [UCT]: 2024-09-10 10:27:33 Age [y:d:h:m:s]: 00:260:20:47:45
Block: 1107001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186331 RingCT/type: yes/0
Extra: 01010b11b1bcab66cab8f3e4b70c5e46123d04c02bd365d0c6ec8c31e6a0ee2e46021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d43f5fc8eaac557e9454e271477bed1c03c1980c9d7d404609f55be049ee72e4 0.600000000000 1584608 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": 1107011, "vin": [ { "gen": { "height": 1107001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d43f5fc8eaac557e9454e271477bed1c03c1980c9d7d404609f55be049ee72e4" } } ], "extra": [ 1, 1, 11, 17, 177, 188, 171, 102, 202, 184, 243, 228, 183, 12, 94, 70, 18, 61, 4, 192, 43, 211, 101, 208, 198, 236, 140, 49, 230, 160, 238, 46, 70, 2, 17, 0, 0, 0, 8, 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