Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 095439c9dd5f8bdfc836a55fd765031b7923a3ccf274d7742267cad3d216185c

Tx prefix hash: a3c072320cc6ee7a2bfde91b67a774a684d218b8839d437a4755caff116abef4
Tx public key: 1c3e357129909e4a30a1e4c926754fb21a7bba7139ff5d3639f0a2810188a075
Timestamp: 1579199286 Timestamp [UCT]: 2020-01-16 18:28:06 Age [y:d:h:m:s]: 05:129:13:02:09
Block: 47007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242747 RingCT/type: yes/0
Extra: 011c3e357129909e4a30a1e4c926754fb21a7bba7139ff5d3639f0a2810188a07502110000003a391a8d0e000000000000000000

1 output(s) for total of 428.792452921000 dcy

stealth address amount amount idx
00: d7ce5058e8d7e90884f77992447b8d04104c41d15bd8339a14ae323437675f50 428.792452921000 86762 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": 47017, "vin": [ { "gen": { "height": 47007 } } ], "vout": [ { "amount": 428792452921, "target": { "key": "d7ce5058e8d7e90884f77992447b8d04104c41d15bd8339a14ae323437675f50" } } ], "extra": [ 1, 28, 62, 53, 113, 41, 144, 158, 74, 48, 161, 228, 201, 38, 117, 79, 178, 26, 123, 186, 113, 57, 255, 93, 54, 57, 240, 162, 129, 1, 136, 160, 117, 2, 17, 0, 0, 0, 58, 57, 26, 141, 14, 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