Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534ad4ebddaae85572edd518ad898436e0f0c3700ca9edfa52fc067e19daf05e

Tx prefix hash: 50740d4dc42eeecaef956b8ad2c34122ea0027242d4fca6893f1e73acf742912
Tx public key: 5403ba3e41635ded4bc8dd41d01d9a420c57802a2f9c6f231a3372d3f1ef1e4a
Timestamp: 1582102015 Timestamp [UCT]: 2020-02-19 08:46:55 Age [y:d:h:m:s]: 04:281:14:02:31
Block: 68051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093657 RingCT/type: yes/0
Extra: 015403ba3e41635ded4bc8dd41d01d9a420c57802a2f9c6f231a3372d3f1ef1e4a0211000000048a2ee0d9000000000000000000

1 output(s) for total of 365.196903320000 dcy

stealth address amount amount idx
00: c1127f8edad6d366ffe46c48e2373e3f4e5fd8dab62ec4bed22cfe7db050e05c 365.196903320000 125345 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": 68061, "vin": [ { "gen": { "height": 68051 } } ], "vout": [ { "amount": 365196903320, "target": { "key": "c1127f8edad6d366ffe46c48e2373e3f4e5fd8dab62ec4bed22cfe7db050e05c" } } ], "extra": [ 1, 84, 3, 186, 62, 65, 99, 93, 237, 75, 200, 221, 65, 208, 29, 154, 66, 12, 87, 128, 42, 47, 156, 111, 35, 26, 51, 114, 211, 241, 239, 30, 74, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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