Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d729a15993e861b9051ec393fabfb602c1e7a91341d9fc93d7676b7f7a80fd5

Tx prefix hash: d7d51c5fc4967c101131dc88d9642dc53a1b7e0980cf030d7fdda4e37f179f45
Tx public key: f6dd32f033e283b8798bdffc4050d439db5d62ecb0ec15c1610402cc16df2310
Timestamp: 1704488165 Timestamp [UCT]: 2024-01-05 20:56:05 Age [y:d:h:m:s]: 01:116:14:51:11
Block: 928935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344472 RingCT/type: yes/0
Extra: 01f6dd32f033e283b8798bdffc4050d439db5d62ecb0ec15c1610402cc16df23100211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a76b1293097b354cd770edba1b1580afdc3823e7d8a3a7d0f839afbe0e827db 0.600000000000 1386801 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": 928945, "vin": [ { "gen": { "height": 928935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a76b1293097b354cd770edba1b1580afdc3823e7d8a3a7d0f839afbe0e827db" } } ], "extra": [ 1, 246, 221, 50, 240, 51, 226, 131, 184, 121, 139, 223, 252, 64, 80, 212, 57, 219, 93, 98, 236, 176, 236, 21, 193, 97, 4, 2, 204, 22, 223, 35, 16, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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