Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e91ce90335cdea18d0150318f5d41ebf794aabdecd1169b1984f282ea7d9c165

Tx prefix hash: 890f53edd76609d5547c12bf73c5e37cbc366a96cae6e99c006fc49c7431a404
Tx public key: cf52db5934e8dbdbca1fb400bc59d488e0cf887098aa223094e8ea9422b8d19c
Timestamp: 1699951027 Timestamp [UCT]: 2023-11-14 08:37:07 Age [y:d:h:m:s]: 02:009:07:37:10
Block: 891345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526428 RingCT/type: yes/0
Extra: 01cf52db5934e8dbdbca1fb400bc59d488e0cf887098aa223094e8ea9422b8d19c021100000004faf35c9c000000000000000000

1 output(s) for total of 0.683288319000 dcy

stealth address amount amount idx
00: 43d223c7cf94b1bb4a557cc3e975e258d62553a18a77156329660e50514fab6a 0.683288319000 1347384 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": 891355, "vin": [ { "gen": { "height": 891345 } } ], "vout": [ { "amount": 683288319, "target": { "key": "43d223c7cf94b1bb4a557cc3e975e258d62553a18a77156329660e50514fab6a" } } ], "extra": [ 1, 207, 82, 219, 89, 52, 232, 219, 219, 202, 31, 180, 0, 188, 89, 212, 136, 224, 207, 136, 112, 152, 170, 34, 48, 148, 232, 234, 148, 34, 184, 209, 156, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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