Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 410e71d1e420360b7e03e035e5aa03886b90b8f65393e652f53bd54584e1c6ff

Tx prefix hash: 38714070aca4dbbc6705aa1b0f77da8d1b9c2d3d8c8deb0fe157fdc59fc9d990
Tx public key: 9500482c918c127ab8a91b5c611dd9a82ec22b047047d7b766881f809a5e6980
Timestamp: 1722918037 Timestamp [UCT]: 2024-08-06 04:20:37 Age [y:d:h:m:s]: 00:223:00:42:18
Block: 1081743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159301 RingCT/type: yes/0
Extra: 019500482c918c127ab8a91b5c611dd9a82ec22b047047d7b766881f809a5e6980021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c35242ccee8c7d613451418e1d5203ce3c64a635254d7d005dad4e81159a4a46 0.600000000000 1555564 of 15

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": 1081753, "vin": [ { "gen": { "height": 1081743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c35242ccee8c7d613451418e1d5203ce3c64a635254d7d005dad4e81159a4a46" } } ], "extra": [ 1, 149, 0, 72, 44, 145, 140, 18, 122, 184, 169, 27, 92, 97, 29, 217, 168, 46, 194, 43, 4, 112, 71, 215, 183, 102, 136, 31, 128, 154, 94, 105, 128, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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