Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766784b77cf92d2784bb632a5a66354da7f6b9c0346234f070fb3571f7698a6a

Tx prefix hash: 3df83f203ee3850094813d5fea0ea558de4df1c10a095d13a1b0709e044bc92a
Tx public key: 7429024edf09c370b8f6ea4aec11b6600474be31e7f5af7e1de7d7f0fb8ba1e1
Timestamp: 1581985943 Timestamp [UCT]: 2020-02-18 00:32:23 Age [y:d:h:m:s]: 05:104:04:54:35
Block: 67080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227618 RingCT/type: yes/0
Extra: 017429024edf09c370b8f6ea4aec11b6600474be31e7f5af7e1de7d7f0fb8ba1e10211000000144ac5aa02000000000000000000

1 output(s) for total of 367.941853321000 dcy

stealth address amount amount idx
00: 0758ac2d96f335c69e6f60e80fee9dd7962fcd19378c5b64c49009695fc937b9 367.941853321000 123587 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": 67090, "vin": [ { "gen": { "height": 67080 } } ], "vout": [ { "amount": 367941853321, "target": { "key": "0758ac2d96f335c69e6f60e80fee9dd7962fcd19378c5b64c49009695fc937b9" } } ], "extra": [ 1, 116, 41, 2, 78, 223, 9, 195, 112, 184, 246, 234, 74, 236, 17, 182, 96, 4, 116, 190, 49, 231, 245, 175, 126, 29, 231, 215, 240, 251, 139, 161, 225, 2, 17, 0, 0, 0, 20, 74, 197, 170, 2, 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