Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe67388fad881d629b684144310827495ff0adbbfd108dbc68bc07dd9100775f

Tx prefix hash: 9f78aa4b71c0f1e331d6d5d1b4883347bf5f666f9f111bb5dab053ee30b4e956
Tx public key: b7a64be8fb9c0643ba3a44e6994dc78db152abdff8f58d6fbce8de80c8461aad
Timestamp: 1681716921 Timestamp [UCT]: 2023-04-17 07:35:21 Age [y:d:h:m:s]: 01:271:03:22:29
Block: 740406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455290 RingCT/type: yes/0
Extra: 01b7a64be8fb9c0643ba3a44e6994dc78db152abdff8f58d6fbce8de80c8461aad0211000000075029cbac000000000000000000

1 output(s) for total of 2.161413346000 dcy

stealth address amount amount idx
00: 0fec41eb0ec09ddf1a26c7b1839e885efbdfbb2258a262d8caf46bc40dfa4fd9 2.161413346000 1187299 of 0

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": 740416, "vin": [ { "gen": { "height": 740406 } } ], "vout": [ { "amount": 2161413346, "target": { "key": "0fec41eb0ec09ddf1a26c7b1839e885efbdfbb2258a262d8caf46bc40dfa4fd9" } } ], "extra": [ 1, 183, 166, 75, 232, 251, 156, 6, 67, 186, 58, 68, 230, 153, 77, 199, 141, 177, 82, 171, 223, 248, 245, 141, 111, 188, 232, 222, 128, 200, 70, 26, 173, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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