Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f12a416cf97392799a00512ae6b5e565637787a2c7ee8689478eb17088e2b6

Tx prefix hash: 2777ebc9c59cf7933697395921d2c5ace5f42ebdb6343f5e7b7d1b16d42b12b4
Tx public key: 0ebbb1c1f9bdf588d662c5078e05b922d82ef9898cbe990438516f75cfe88d5e
Timestamp: 1737947295 Timestamp [UCT]: 2025-01-27 03:08:15 Age [y:d:h:m:s]: 00:143:16:17:45
Block: 1205954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102617 RingCT/type: yes/0
Extra: 010ebbb1c1f9bdf588d662c5078e05b922d82ef9898cbe990438516f75cfe88d5e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33b886af5a2b097c77c1c5157247f329ac41f3e9f9b602d8cc992ee3b56dffcf 0.600000000000 1692653 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": 1205964, "vin": [ { "gen": { "height": 1205954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33b886af5a2b097c77c1c5157247f329ac41f3e9f9b602d8cc992ee3b56dffcf" } } ], "extra": [ 1, 14, 187, 177, 193, 249, 189, 245, 136, 214, 98, 197, 7, 142, 5, 185, 34, 216, 46, 249, 137, 140, 190, 153, 4, 56, 81, 111, 117, 207, 232, 141, 94, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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