Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4c7ba02d2ad4ef3251d2a3cd45d8a1b2101cc1fc905e0e6c448b68b3e0ff56

Tx prefix hash: bf719a6799fbda4e2be03f66dc1e6e97ae93fb23679487d8ada32662b1f1438e
Tx public key: 4a57fd3ffcb50a36ff82d9df6cda663100b9cee27c9c355d7404c08b126c8c83
Timestamp: 1720693190 Timestamp [UCT]: 2024-07-11 10:19:50 Age [y:d:h:m:s]: 00:226:01:23:57
Block: 1063314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161436 RingCT/type: yes/0
Extra: 014a57fd3ffcb50a36ff82d9df6cda663100b9cee27c9c355d7404c08b126c8c8302110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a106068a56b9b947a045afa2e0f98881733723c5fc87fb72ba1c4fd8cede8bb0 0.600000000000 1533829 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": 1063324, "vin": [ { "gen": { "height": 1063314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a106068a56b9b947a045afa2e0f98881733723c5fc87fb72ba1c4fd8cede8bb0" } } ], "extra": [ 1, 74, 87, 253, 63, 252, 181, 10, 54, 255, 130, 217, 223, 108, 218, 102, 49, 0, 185, 206, 226, 124, 156, 53, 93, 116, 4, 192, 139, 18, 108, 140, 131, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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