Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368f4f11f39d534a4f7f976122570ac44fad1fdee54f0f34fbceaae3635b0c3d

Tx prefix hash: 1a9fe2c0c302edf53f4296adf141aec3674df06c47e657d09c777d0427b406c6
Tx public key: 14f62b91433bcaac96d0805a9341dc1471c95fcd7c77f1ce84537c8935afe2f9
Timestamp: 1737715331 Timestamp [UCT]: 2025-01-24 10:42:11 Age [y:d:h:m:s]: 00:049:06:27:44
Block: 1204233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35029 RingCT/type: yes/0
Extra: 0114f62b91433bcaac96d0805a9341dc1471c95fcd7c77f1ce84537c8935afe2f902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f12401e4493b9ed69c9e3d98041dd0b732d0a895f71396ee71db7c5b77d7f852 0.600000000000 1690918 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": 1204243, "vin": [ { "gen": { "height": 1204233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f12401e4493b9ed69c9e3d98041dd0b732d0a895f71396ee71db7c5b77d7f852" } } ], "extra": [ 1, 20, 246, 43, 145, 67, 59, 202, 172, 150, 208, 128, 90, 147, 65, 220, 20, 113, 201, 95, 205, 124, 119, 241, 206, 132, 83, 124, 137, 53, 175, 226, 249, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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