Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd1ca16a0def5139a165d65305cf3e64cfb0c159409b2716dc773f3c76862aa

Tx prefix hash: dc4c4bcf630a5c3607c8eb9f968c9e357f29ca8bd0a309d4ac1d2f6b8894a82f
Tx public key: d40ba82d624ce7aad5c1816e2f20e10db3e3715208db09a94875ebc2772ab7d4
Timestamp: 1696709735 Timestamp [UCT]: 2023-10-07 20:15:35 Age [y:d:h:m:s]: 01:094:17:00:07
Block: 864668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328955 RingCT/type: yes/0
Extra: 01d40ba82d624ce7aad5c1816e2f20e10db3e3715208db09a94875ebc2772ab7d402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.837521588000 dcy

stealth address amount amount idx
00: 41573ff72bf69edfd8260a2bafa16ec2aed0daa66052d21dc7aa97a598508a3e 0.837521588000 1319188 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": 864678, "vin": [ { "gen": { "height": 864668 } } ], "vout": [ { "amount": 837521588, "target": { "key": "41573ff72bf69edfd8260a2bafa16ec2aed0daa66052d21dc7aa97a598508a3e" } } ], "extra": [ 1, 212, 11, 168, 45, 98, 76, 231, 170, 213, 193, 129, 110, 47, 32, 225, 13, 179, 227, 113, 82, 8, 219, 9, 169, 72, 117, 235, 194, 119, 42, 183, 212, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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