Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03702b200ec18f92f948c946f0720819ac15e0bc35500c862a5fe5e17389c4b5

Tx prefix hash: a5ae6589eb59ab0bba32426a2beae8bf5aa72184ebba61bde3ade46a7277ddb2
Tx public key: 31e2b4a6715e616a61bb3513c6f49f0ddd57f96fbede47d2f91033dcc33f0299
Timestamp: 1682795935 Timestamp [UCT]: 2023-04-29 19:18:55 Age [y:d:h:m:s]: 01:342:10:54:05
Block: 749358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506011 RingCT/type: yes/0
Extra: 0131e2b4a6715e616a61bb3513c6f49f0ddd57f96fbede47d2f91033dcc33f02990211000000037e406890000000000000000000

1 output(s) for total of 2.018673476000 dcy

stealth address amount amount idx
00: ac3a2bde3fb03d9d4d3df740537bd845321919d55a14abd58135be434175a7af 2.018673476000 1197313 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": 749368, "vin": [ { "gen": { "height": 749358 } } ], "vout": [ { "amount": 2018673476, "target": { "key": "ac3a2bde3fb03d9d4d3df740537bd845321919d55a14abd58135be434175a7af" } } ], "extra": [ 1, 49, 226, 180, 166, 113, 94, 97, 106, 97, 187, 53, 19, 198, 244, 159, 13, 221, 87, 249, 111, 190, 222, 71, 210, 249, 16, 51, 220, 195, 63, 2, 153, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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