Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11da993872797ca3dea12d963e4e34ef596c13d18e043b97536896bf60000649

Tx prefix hash: 00d1016655c67355d8e0acd7c26deb24cace0c89d1d0a297f9fae0384abefdba
Tx public key: 960b3af4507b4f73eee9b0bd97c83f6eb2ee84bfd4c4dbb15085a2b44874806e
Timestamp: 1578038817 Timestamp [UCT]: 2020-01-03 08:06:57 Age [y:d:h:m:s]: 05:072:07:46:35
Block: 37606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201624 RingCT/type: yes/0
Extra: 01960b3af4507b4f73eee9b0bd97c83f6eb2ee84bfd4c4dbb15085a2b44874806e021100000054410370dd000000000000000000

1 output(s) for total of 460.677034121000 dcy

stealth address amount amount idx
00: 2411f73c69fb6356194001a2e419d53a621a4a595314c90596fd5297956d59a3 460.677034121000 63922 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": 37616, "vin": [ { "gen": { "height": 37606 } } ], "vout": [ { "amount": 460677034121, "target": { "key": "2411f73c69fb6356194001a2e419d53a621a4a595314c90596fd5297956d59a3" } } ], "extra": [ 1, 150, 11, 58, 244, 80, 123, 79, 115, 238, 233, 176, 189, 151, 200, 63, 110, 178, 238, 132, 191, 212, 196, 219, 177, 80, 133, 162, 180, 72, 116, 128, 110, 2, 17, 0, 0, 0, 84, 65, 3, 112, 221, 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