Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03020c39f2009e9829884d25b49b2bebc373d404aed2b1870f2a8c9938c95475

Tx prefix hash: 1c35dc32a0161d9bd38bd560544317d7afcc3d9bac08ef4266885cd7fd02b1d9
Tx public key: b10220c40d4494fd5963e7b96dc18ed1e5934b3f561a5242dbafa1e011a7df22
Timestamp: 1695102233 Timestamp [UCT]: 2023-09-19 05:43:53 Age [y:d:h:m:s]: 01:200:08:40:14
Block: 851333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404265 RingCT/type: yes/0
Extra: 01b10220c40d4494fd5963e7b96dc18ed1e5934b3f561a5242dbafa1e011a7df22021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.927214940000 dcy

stealth address amount amount idx
00: dc41394cf08e6728238fc95ed12fa40bf77bd650f830f1d7a6241e891f682510 0.927214940000 1305107 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": 851343, "vin": [ { "gen": { "height": 851333 } } ], "vout": [ { "amount": 927214940, "target": { "key": "dc41394cf08e6728238fc95ed12fa40bf77bd650f830f1d7a6241e891f682510" } } ], "extra": [ 1, 177, 2, 32, 196, 13, 68, 148, 253, 89, 99, 231, 185, 109, 193, 142, 209, 229, 147, 75, 63, 86, 26, 82, 66, 219, 175, 161, 224, 17, 167, 223, 34, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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