Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c09fd2156852dc1f890f216e3a9e9b3a0378122a5545d06f5d12764a47c23139

Tx prefix hash: 7bc4627134bb1654768f4a3e28121da2137de41b99fb8b94ce7452413b0f4d42
Tx public key: d8a7ecbfc71aa21389a71dd9f4d1d7ca7f87eff7e4df23da43c2e0dd1947bfab
Timestamp: 1735547736 Timestamp [UCT]: 2024-12-30 08:35:36 Age [y:d:h:m:s]: 00:101:17:08:32
Block: 1186321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72489 RingCT/type: yes/0
Extra: 01d8a7ecbfc71aa21389a71dd9f4d1d7ca7f87eff7e4df23da43c2e0dd1947bfab021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96d6758d149fd3ed2ba848c683c24fd9280d974aab03127e0f643c638d78f94c 0.600000000000 1672800 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": 1186331, "vin": [ { "gen": { "height": 1186321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96d6758d149fd3ed2ba848c683c24fd9280d974aab03127e0f643c638d78f94c" } } ], "extra": [ 1, 216, 167, 236, 191, 199, 26, 162, 19, 137, 167, 29, 217, 244, 209, 215, 202, 127, 135, 239, 247, 228, 223, 35, 218, 67, 194, 224, 221, 25, 71, 191, 171, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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