Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a50fe6e0c9f6f35cca020a089974a03b3ea4608da9f06616146257f8b3e8135

Tx prefix hash: cb0407115896808b377fddbeb39cb3f242b88851424c873270229e06edf98170
Tx public key: c3ecacbf47aae9ee34bf46e79fce87bd0b1a7b9fa71c2dc19628660fec53e7d4
Timestamp: 1713237190 Timestamp [UCT]: 2024-04-16 03:13:10 Age [y:d:h:m:s]: 00:193:07:04:54
Block: 1001480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138437 RingCT/type: yes/0
Extra: 01c3ecacbf47aae9ee34bf46e79fce87bd0b1a7b9fa71c2dc19628660fec53e7d4021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb3caf8d955530123d084398f74ab2a6cf3aa9ba089b415cf70e83156a4e4bcd 0.600000000000 1461984 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": 1001490, "vin": [ { "gen": { "height": 1001480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb3caf8d955530123d084398f74ab2a6cf3aa9ba089b415cf70e83156a4e4bcd" } } ], "extra": [ 1, 195, 236, 172, 191, 71, 170, 233, 238, 52, 191, 70, 231, 159, 206, 135, 189, 11, 26, 123, 159, 167, 28, 45, 193, 150, 40, 102, 15, 236, 83, 231, 212, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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