Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c343b672f3554308cb080134b517e4f7b5f3e1b560ca3bb6af0f646d3fe9b75

Tx prefix hash: bf31baf0a783b19f7f5a4dd5caa7a53fef38d8f10259b21b2735c72efdd54000
Tx public key: cbc448d733af8e9d9f6728ef07f2a3bb993704489fc4d907c04851629ff14511
Timestamp: 1726968539 Timestamp [UCT]: 2024-09-22 01:28:59 Age [y:d:h:m:s]: 00:197:17:14:05
Block: 1115331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141112 RingCT/type: yes/0
Extra: 01cbc448d733af8e9d9f6728ef07f2a3bb993704489fc4d907c04851629ff1451102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04aa84727e7c38cfc937a84bc1338fa59e90d1e638d1a797ddaf2534b03584de 0.600000000000 1595426 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": 1115341, "vin": [ { "gen": { "height": 1115331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04aa84727e7c38cfc937a84bc1338fa59e90d1e638d1a797ddaf2534b03584de" } } ], "extra": [ 1, 203, 196, 72, 215, 51, 175, 142, 157, 159, 103, 40, 239, 7, 242, 163, 187, 153, 55, 4, 72, 159, 196, 217, 7, 192, 72, 81, 98, 159, 241, 69, 17, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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