Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 842490a155215d26b2a6ab97024dec5ee44e9326f6805cb7edf884b2455fe03f

Tx prefix hash: 8506bf97fc335510f80ea79ce95eb8ab41b5cc137b431d566aab392930ac44fa
Tx public key: 7400e14db4e0e77083f7f2c5c1f970ae083bd975d0d5847b999d478b9c65685c
Timestamp: 1583346504 Timestamp [UCT]: 2020-03-04 18:28:24 Age [y:d:h:m:s]: 05:087:03:41:38
Block: 76408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1217357 RingCT/type: yes/0
Extra: 017400e14db4e0e77083f7f2c5c1f970ae083bd975d0d5847b999d478b9c65685c02110000004056c366d3000000000000000000

1 output(s) for total of 342.633145092000 dcy

stealth address amount amount idx
00: 0ae681ff38be058de792cdd9ce779acc9b1ecbb4e2a570daa28f9b46b0f7f788 342.633145092000 140658 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": 76418, "vin": [ { "gen": { "height": 76408 } } ], "vout": [ { "amount": 342633145092, "target": { "key": "0ae681ff38be058de792cdd9ce779acc9b1ecbb4e2a570daa28f9b46b0f7f788" } } ], "extra": [ 1, 116, 0, 225, 77, 180, 224, 231, 112, 131, 247, 242, 197, 193, 249, 112, 174, 8, 59, 217, 117, 208, 213, 132, 123, 153, 157, 71, 139, 156, 101, 104, 92, 2, 17, 0, 0, 0, 64, 86, 195, 102, 211, 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