Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01bb3ddc8e833a9a0f3dd800af39eb1327fdb643cea04764beab42b55563d0e0

Tx prefix hash: 3678b6759b427b15d6221a5d0f509582a3c5cc184c3e1cef56f6787843bedd74
Tx public key: e1f56ff8dfad1bb7e089822e0718a8051fb1ab23e6ab77f9943cd4c79a56e326
Timestamp: 1718366356 Timestamp [UCT]: 2024-06-14 11:59:16 Age [y:d:h:m:s]: 00:327:23:07:39
Block: 1044022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234383 RingCT/type: yes/0
Extra: 01e1f56ff8dfad1bb7e089822e0718a8051fb1ab23e6ab77f9943cd4c79a56e32602110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bee5ad74184bb3edf63823aef9404f1f12325ae2f31259910582269859d7f90a 0.600000000000 1513215 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": 1044032, "vin": [ { "gen": { "height": 1044022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bee5ad74184bb3edf63823aef9404f1f12325ae2f31259910582269859d7f90a" } } ], "extra": [ 1, 225, 245, 111, 248, 223, 173, 27, 183, 224, 137, 130, 46, 7, 24, 168, 5, 31, 177, 171, 35, 230, 171, 119, 249, 148, 60, 212, 199, 154, 86, 227, 38, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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