Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5749e6d056c6e0de36c763ff151f62cd3d6864ad459327df951fe17d506508bb

Tx prefix hash: b9de2e31cc85203dd313ce030304eb906be906fba290f3db12e0fef631f528f3
Tx public key: 9e2807d3544d90fd21e8c24b9edc91e1333e9888b24c1f36265604abda47bf79
Timestamp: 1735103314 Timestamp [UCT]: 2024-12-25 05:08:34 Age [y:d:h:m:s]: 00:093:23:30:40
Block: 1182653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66946 RingCT/type: yes/0
Extra: 019e2807d3544d90fd21e8c24b9edc91e1333e9888b24c1f36265604abda47bf7902110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 594980035cc0f4cd3a52627bf934dcd323aef5c8b0357814091047641b844df6 0.600000000000 1669088 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": 1182663, "vin": [ { "gen": { "height": 1182653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "594980035cc0f4cd3a52627bf934dcd323aef5c8b0357814091047641b844df6" } } ], "extra": [ 1, 158, 40, 7, 211, 84, 77, 144, 253, 33, 232, 194, 75, 158, 220, 145, 225, 51, 62, 152, 136, 178, 76, 31, 54, 38, 86, 4, 171, 218, 71, 191, 121, 2, 17, 0, 0, 0, 11, 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