Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba9247bf5b1dfe3dea214ea13b9b1602213f9b00d69c9f88fe5369b915a36122

Tx prefix hash: c2407d29b907ea3ea6e3bd8d96a92893735bb6064cfdcab7a27bf81a0c2fe8f8
Tx public key: da608203cd592c2bf1b3c3b7e5c5075bad579a6b4967c11dd420fc0c17035c1e
Timestamp: 1737679123 Timestamp [UCT]: 2025-01-24 00:38:43 Age [y:d:h:m:s]: 00:144:17:55:07
Block: 1203929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103188 RingCT/type: yes/0
Extra: 01da608203cd592c2bf1b3c3b7e5c5075bad579a6b4967c11dd420fc0c17035c1e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5bfc41ebef3391b23f633a3d28ae57cb9e6592298393112dbc6da6ae74a2f71 0.600000000000 1690610 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": 1203939, "vin": [ { "gen": { "height": 1203929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5bfc41ebef3391b23f633a3d28ae57cb9e6592298393112dbc6da6ae74a2f71" } } ], "extra": [ 1, 218, 96, 130, 3, 205, 89, 44, 43, 241, 179, 195, 183, 229, 197, 7, 91, 173, 87, 154, 107, 73, 103, 193, 29, 212, 32, 252, 12, 23, 3, 92, 30, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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