Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a06bfa9fe2e83fd47e7c8474f768f6bcd154784c4adb35e93b8a36d1c3c8f5

Tx prefix hash: bcf04d3023dd19e7d0868b17d3d0143819d86ce53df0d2f97cd346a2a6239c4b
Tx public key: 0ed62e913d3b5fd7ace74180c2257c3bdc97f51efa9de05bece0b64502603a74
Timestamp: 1732768574 Timestamp [UCT]: 2024-11-28 04:36:14 Age [y:d:h:m:s]: 00:138:13:29:30
Block: 1163317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98841 RingCT/type: yes/0
Extra: 010ed62e913d3b5fd7ace74180c2257c3bdc97f51efa9de05bece0b64502603a740211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad856c158195d192e0e87815e14f3b1d0526663979c5a9fd5838a615d47273b 0.600000000000 1648984 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": 1163327, "vin": [ { "gen": { "height": 1163317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad856c158195d192e0e87815e14f3b1d0526663979c5a9fd5838a615d47273b" } } ], "extra": [ 1, 14, 214, 46, 145, 61, 59, 95, 215, 172, 231, 65, 128, 194, 37, 124, 59, 220, 151, 245, 30, 250, 157, 224, 91, 236, 224, 182, 69, 2, 96, 58, 116, 2, 17, 0, 0, 0, 7, 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