Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b36ede143202b88353670e102b6e0ce16a9ee67603c850cc7428f583c3087f

Tx prefix hash: cec6f4ce5d010cb8dcc9a0c3e3d30314527c18d47e8997e9661d9210d019cd8b
Tx public key: 402a57a8e23b962cbfe245ee1d3d82c5b549c9f5337569a60cdb805cd31719e8
Timestamp: 1708852973 Timestamp [UCT]: 2024-02-25 09:22:53 Age [y:d:h:m:s]: 01:090:01:51:09
Block: 965152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325423 RingCT/type: yes/0
Extra: 01402a57a8e23b962cbfe245ee1d3d82c5b549c9f5337569a60cdb805cd31719e80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a6022849714ef91ceab9d37c69577918c746e219f85bf4b72af7fc986073116 0.600000000000 1424901 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": 965162, "vin": [ { "gen": { "height": 965152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a6022849714ef91ceab9d37c69577918c746e219f85bf4b72af7fc986073116" } } ], "extra": [ 1, 64, 42, 87, 168, 226, 59, 150, 44, 191, 226, 69, 238, 29, 61, 130, 197, 181, 73, 201, 245, 51, 117, 105, 166, 12, 219, 128, 92, 211, 23, 25, 232, 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