Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4d2d712db7ac63da6ec72e3bdeb155c00ffd5879a190be3fd3ad6ae16c2671

Tx prefix hash: 10c307b8fbbe9944361c326a96f3fdb42c648059f7fabf64f105f631fa5c47f1
Tx public key: 3ee89e2263ca8f61d342bb36b37530561aa520208086c56b92e6d00fc8d508d2
Timestamp: 1714444520 Timestamp [UCT]: 2024-04-30 02:35:20 Age [y:d:h:m:s]: 00:198:23:31:39
Block: 1011494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142429 RingCT/type: yes/0
Extra: 013ee89e2263ca8f61d342bb36b37530561aa520208086c56b92e6d00fc8d508d20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90bd38a65af0e54f0f933d8d0fdbf289a6a0b2a01fe6e046359a259263565ddd 0.600000000000 1473740 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": 1011504, "vin": [ { "gen": { "height": 1011494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90bd38a65af0e54f0f933d8d0fdbf289a6a0b2a01fe6e046359a259263565ddd" } } ], "extra": [ 1, 62, 232, 158, 34, 99, 202, 143, 97, 211, 66, 187, 54, 179, 117, 48, 86, 26, 165, 32, 32, 128, 134, 197, 107, 146, 230, 208, 15, 200, 213, 8, 210, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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