Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e30e7fbe457a735318c22a9c6667deb1738400afe4d61ee6d485a1fa0ceda902

Tx prefix hash: c128e21e2e448c5b62a3670e631b74623281d3756b9f457a9ecb7f35e8942897
Tx public key: 4a4e87039ff4771374a8d6c86e49ec8a89f179775274eb8e852c28c8fe78272f
Timestamp: 1713397314 Timestamp [UCT]: 2024-04-17 23:41:54 Age [y:d:h:m:s]: 00:313:06:44:13
Block: 1002799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223947 RingCT/type: yes/0
Extra: 014a4e87039ff4771374a8d6c86e49ec8a89f179775274eb8e852c28c8fe78272f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69195da806e880c0eeb1e7bbd2418951b9e366d9bc2bcf6947a183f503fe5193 0.600000000000 1463323 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": 1002809, "vin": [ { "gen": { "height": 1002799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69195da806e880c0eeb1e7bbd2418951b9e366d9bc2bcf6947a183f503fe5193" } } ], "extra": [ 1, 74, 78, 135, 3, 159, 244, 119, 19, 116, 168, 214, 200, 110, 73, 236, 138, 137, 241, 121, 119, 82, 116, 235, 142, 133, 44, 40, 200, 254, 120, 39, 47, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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