Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59f3e662b2343838ac83999b91f49c72de0a6005308106160a99f5466e7b672e

Tx prefix hash: d222a3ad3bead3af1e53fc56cc9e9edfa6c3d50c91b33a597eb0286594be3226
Tx public key: daeadb633e4d350a1d61e4ea3d693dde5f95e97bb6c91731c59dce0d2d8f5c25
Timestamp: 1721699594 Timestamp [UCT]: 2024-07-23 01:53:14 Age [y:d:h:m:s]: 00:262:01:55:38
Block: 1071633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187241 RingCT/type: yes/0
Extra: 01daeadb633e4d350a1d61e4ea3d693dde5f95e97bb6c91731c59dce0d2d8f5c25021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf530dec28fa2a9210658355c7a34f38121dfa61b8cca014d1776bbb83dd4ec6 0.600000000000 1543932 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": 1071643, "vin": [ { "gen": { "height": 1071633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf530dec28fa2a9210658355c7a34f38121dfa61b8cca014d1776bbb83dd4ec6" } } ], "extra": [ 1, 218, 234, 219, 99, 62, 77, 53, 10, 29, 97, 228, 234, 61, 105, 61, 222, 95, 149, 233, 123, 182, 201, 23, 49, 197, 157, 206, 13, 45, 143, 92, 37, 2, 17, 0, 0, 0, 7, 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