Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b6c8048597d35ddbce4301612594a8be2eab0b728177aa90b1f7b66fead724e

Tx prefix hash: bd7991082ab982dae6529a70af37a33ca5ca03920f899ba216fe078f41774cd6
Tx public key: da26a86a691f1b1423911b9e277aaab948f72ed86c4e1e40d32bc867bf5e8ff9
Timestamp: 1722975657 Timestamp [UCT]: 2024-08-06 20:20:57 Age [y:d:h:m:s]: 00:314:20:24:40
Block: 1082220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224852 RingCT/type: yes/0
Extra: 01da26a86a691f1b1423911b9e277aaab948f72ed86c4e1e40d32bc867bf5e8ff9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b1b4dee4183df2cade4010b635407d2d56d5426c8f0190ec269e21bd8946177 0.600000000000 1556045 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": 1082230, "vin": [ { "gen": { "height": 1082220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b1b4dee4183df2cade4010b635407d2d56d5426c8f0190ec269e21bd8946177" } } ], "extra": [ 1, 218, 38, 168, 106, 105, 31, 27, 20, 35, 145, 27, 158, 39, 122, 170, 185, 72, 247, 46, 216, 108, 78, 30, 64, 211, 43, 200, 103, 191, 94, 143, 249, 2, 17, 0, 0, 0, 4, 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