Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1dc9dd54ec7c411effc944dceece4dfedc1da79863ae41fa8f29b7bcb0edccd

Tx prefix hash: 7b98498e4ab37c6a661189f84cc43e8d65b6e6eea639b88922bccb91590b8fde
Tx public key: 7ce87017d5ba3c685bd0a6e15a26ce673e7b4a98122dc1879e29564e33182b8b
Timestamp: 1728684418 Timestamp [UCT]: 2024-10-11 22:06:58 Age [y:d:h:m:s]: 00:173:08:13:25
Block: 1129559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123657 RingCT/type: yes/0
Extra: 017ce87017d5ba3c685bd0a6e15a26ce673e7b4a98122dc1879e29564e33182b8b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fddfc2915a305ad967d4fded10d035a58bc6be4e35f84cf2f60376aa3826c13 0.600000000000 1612386 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": 1129569, "vin": [ { "gen": { "height": 1129559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fddfc2915a305ad967d4fded10d035a58bc6be4e35f84cf2f60376aa3826c13" } } ], "extra": [ 1, 124, 232, 112, 23, 213, 186, 60, 104, 91, 208, 166, 225, 90, 38, 206, 103, 62, 123, 74, 152, 18, 45, 193, 135, 158, 41, 86, 78, 51, 24, 43, 139, 2, 17, 0, 0, 0, 2, 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