Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee859525ae8aece3ad66801a31037e87b1a67fbe284b03b5efef17be52a9302c

Tx prefix hash: bd6606337e226319e2da09f7ecb4b20576aa695da162cbbae95fa1e91746bf35
Tx public key: abf1daa6bff70c63d9fdd8e5cd27aa287418d4cb2eb308ab19b3968cc8c2de66
Timestamp: 1584771644 Timestamp [UCT]: 2020-03-21 06:20:44 Age [y:d:h:m:s]: 05:234:12:02:07
Block: 86391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1322154 RingCT/type: yes/0
Extra: 01abf1daa6bff70c63d9fdd8e5cd27aa287418d4cb2eb308ab19b3968cc8c2de66021100000003e5e30634000000000000000000

1 output(s) for total of 317.505706311000 dcy

stealth address amount amount idx
00: f42032067cb944202a0ba2eeb07928617f8f4cd5e8c12b4b8059a97338f6cb9a 317.505706311000 155831 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": 86401, "vin": [ { "gen": { "height": 86391 } } ], "vout": [ { "amount": 317505706311, "target": { "key": "f42032067cb944202a0ba2eeb07928617f8f4cd5e8c12b4b8059a97338f6cb9a" } } ], "extra": [ 1, 171, 241, 218, 166, 191, 247, 12, 99, 217, 253, 216, 229, 205, 39, 170, 40, 116, 24, 212, 203, 46, 179, 8, 171, 25, 179, 150, 140, 200, 194, 222, 102, 2, 17, 0, 0, 0, 3, 229, 227, 6, 52, 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