Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f6a8b185622f5de16a6a44eb1aafbd912e3d847b3492cf831af0ddd78f8620

Tx prefix hash: 1d959debcffbf9104e244ad906bde69f193ab53304af10261d23dce085d5a00a
Tx public key: c08c0a412a813eba0ab63c9a82e92c236aafe416240139ebd2ceee00a57ed249
Timestamp: 1705697058 Timestamp [UCT]: 2024-01-19 20:44:18 Age [y:d:h:m:s]: 01:091:21:18:05
Block: 938952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326766 RingCT/type: yes/0
Extra: 01c08c0a412a813eba0ab63c9a82e92c236aafe416240139ebd2ceee00a57ed24902110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4027e718531ec5337b65ce0aa27d51642240092d0924105f596ba2195579f3ea 0.600000000000 1397036 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": 938962, "vin": [ { "gen": { "height": 938952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4027e718531ec5337b65ce0aa27d51642240092d0924105f596ba2195579f3ea" } } ], "extra": [ 1, 192, 140, 10, 65, 42, 129, 62, 186, 10, 182, 60, 154, 130, 233, 44, 35, 106, 175, 228, 22, 36, 1, 57, 235, 210, 206, 238, 0, 165, 126, 210, 73, 2, 17, 0, 0, 0, 10, 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