Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b20f41d1652424f8ef10e748e7ebc886d198b9a1f552cc276bc21699f54577

Tx prefix hash: 3cedd5e648555f0710a221ea283681f5945fc9981fda084c9419ffdfb72de882
Tx public key: 5c2c6bb06911bb01b360a88aa16a505bdb06fd59def223b88b3bd35ab97548a8
Timestamp: 1705330122 Timestamp [UCT]: 2024-01-15 14:48:42 Age [y:d:h:m:s]: 01:001:15:52:45
Block: 935920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262500 RingCT/type: yes/0
Extra: 015c2c6bb06911bb01b360a88aa16a505bdb06fd59def223b88b3bd35ab97548a80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 059dbaf37e91423b5d16a69f517060de2ed74a387bf128dbfd6c22cbaa77e5db 0.600000000000 1393938 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": 935930, "vin": [ { "gen": { "height": 935920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "059dbaf37e91423b5d16a69f517060de2ed74a387bf128dbfd6c22cbaa77e5db" } } ], "extra": [ 1, 92, 44, 107, 176, 105, 17, 187, 1, 179, 96, 168, 138, 161, 106, 80, 91, 219, 6, 253, 89, 222, 242, 35, 184, 139, 59, 211, 90, 185, 117, 72, 168, 2, 17, 0, 0, 0, 9, 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