Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f464fb5fc42293cac0420dab610fb6f9c52751c7378efdfbd391d8f04754cab

Tx prefix hash: 41803e9451bb723f65729aea8a9d8d57a3fad6159e33b27615754c1cf07d5021
Tx public key: 74992770b593c2059426146bf3ba8e174a60b1eef06ebcb72dbdf8bac2cd89e4
Timestamp: 1698372263 Timestamp [UCT]: 2023-10-27 02:04:23 Age [y:d:h:m:s]: 01:174:08:06:49
Block: 878463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385610 RingCT/type: yes/0
Extra: 0174992770b593c2059426146bf3ba8e174a60b1eef06ebcb72dbdf8bac2cd89e40211000000034b8f5122000000000000000000

1 output(s) for total of 0.753854321000 dcy

stealth address amount amount idx
00: 0df421e9bd22f1e6441fe4f45ac82464e1379c659721b79eabac384c0d54a3ec 0.753854321000 1333911 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": 878473, "vin": [ { "gen": { "height": 878463 } } ], "vout": [ { "amount": 753854321, "target": { "key": "0df421e9bd22f1e6441fe4f45ac82464e1379c659721b79eabac384c0d54a3ec" } } ], "extra": [ 1, 116, 153, 39, 112, 181, 147, 194, 5, 148, 38, 20, 107, 243, 186, 142, 23, 74, 96, 177, 238, 240, 110, 188, 183, 45, 189, 248, 186, 194, 205, 137, 228, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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