Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ff7f02533b2c529196407390fe47d5dbd298888210f0ab7fea748d873589e7

Tx prefix hash: c110808b38e330940c9b2140f631cf0f57bd3bdbb55a45b80703ad8614b6fab0
Tx public key: 4a70971342b6c1ecafcfcdc81c6f0a8f5279b1e932b98169bdaa9f1673d163d2
Timestamp: 1681020454 Timestamp [UCT]: 2023-04-09 06:07:34 Age [y:d:h:m:s]: 02:010:03:23:03
Block: 734667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529388 RingCT/type: yes/0
Extra: 014a70971342b6c1ecafcfcdc81c6f0a8f5279b1e932b98169bdaa9f1673d163d2021100000002b3164c24000000000000000000

1 output(s) for total of 2.258101607000 dcy

stealth address amount amount idx
00: aa9484fedcbcd9856ab4e09370f157b3196397f9e7fa570bdc632d383f810244 2.258101607000 1180906 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": 734677, "vin": [ { "gen": { "height": 734667 } } ], "vout": [ { "amount": 2258101607, "target": { "key": "aa9484fedcbcd9856ab4e09370f157b3196397f9e7fa570bdc632d383f810244" } } ], "extra": [ 1, 74, 112, 151, 19, 66, 182, 193, 236, 175, 207, 205, 200, 28, 111, 10, 143, 82, 121, 177, 233, 50, 185, 129, 105, 189, 170, 159, 22, 115, 209, 99, 210, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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