Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387b3c726d5a5400b0f9a68ceabd7baa35effd81c2bb8407fb54e0607fd9a100

Tx prefix hash: 8d07db0bb66a47eb9e6fd4b4a6c411cfd15f915ef95434359e07a1a8b20414ed
Tx public key: 398a607ec0a0582053484c2743539f86344a3f2e9a359c1f99cc6996e604dd1e
Timestamp: 1726852401 Timestamp [UCT]: 2024-09-20 17:13:21 Age [y:d:h:m:s]: 00:112:02:57:56
Block: 1114367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80171 RingCT/type: yes/0
Extra: 01398a607ec0a0582053484c2743539f86344a3f2e9a359c1f99cc6996e604dd1e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ddb3ba1ad87f1f0d19f3a810df1cb4cf1c02093095573711a7316e290411425 0.600000000000 1594168 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": 1114377, "vin": [ { "gen": { "height": 1114367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ddb3ba1ad87f1f0d19f3a810df1cb4cf1c02093095573711a7316e290411425" } } ], "extra": [ 1, 57, 138, 96, 126, 192, 160, 88, 32, 83, 72, 76, 39, 67, 83, 159, 134, 52, 74, 63, 46, 154, 53, 156, 31, 153, 204, 105, 150, 230, 4, 221, 30, 2, 17, 0, 0, 0, 1, 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