Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5c05cae4d076b7bd3155160dc77845c40c452f75c87927571689594b09374bc

Tx prefix hash: a1a962da2a176ea53c29a36c971890a217a1a53394b11881edecc0f426f619df
Tx public key: df5bd4ec3b877a9d866cafa7cda22ad6c874554b76d2fca2b596701982f08d5b
Timestamp: 1577786020 Timestamp [UCT]: 2019-12-31 09:53:40 Age [y:d:h:m:s]: 05:045:05:23:19
Block: 35593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182148 RingCT/type: yes/0
Extra: 01df5bd4ec3b877a9d866cafa7cda22ad6c874554b76d2fca2b596701982f08d5b021100000015d81c26c0000000000000000000

1 output(s) for total of 467.806734666000 dcy

stealth address amount amount idx
00: ed3fb0c6cb31627423ae11a06ca38bb4bd68940980b8e5a2fb77be5ee00b1918 467.806734666000 60092 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": 35603, "vin": [ { "gen": { "height": 35593 } } ], "vout": [ { "amount": 467806734666, "target": { "key": "ed3fb0c6cb31627423ae11a06ca38bb4bd68940980b8e5a2fb77be5ee00b1918" } } ], "extra": [ 1, 223, 91, 212, 236, 59, 135, 122, 157, 134, 108, 175, 167, 205, 162, 42, 214, 200, 116, 85, 75, 118, 210, 252, 162, 181, 150, 112, 25, 130, 240, 141, 91, 2, 17, 0, 0, 0, 21, 216, 28, 38, 192, 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