Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce9890d17684ceafdf9f64018dc69cfc466c335eed3fa763624fa0cb122439f2

Tx prefix hash: 2110ac90eb1d29e290bb71baa770dfd80aacade13293096422dc92f5d4b76e5f
Tx public key: 337ea43425a1b1e74db06e4a67d6cde8ab22706fbdab5da62715671fb80e2525
Timestamp: 1689570502 Timestamp [UCT]: 2023-07-17 05:08:22 Age [y:d:h:m:s]: 01:268:22:32:33
Block: 805543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453328 RingCT/type: yes/0
Extra: 01337ea43425a1b1e74db06e4a67d6cde8ab22706fbdab5da62715671fb80e252502110000000333af99f4000000000000000000

1 output(s) for total of 1.314927372000 dcy

stealth address amount amount idx
00: 8ebbea9b8d6f1565026274bcaa6317b04e6c6ae409187dcc3a89baee7e88c583 1.314927372000 1256770 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": 805553, "vin": [ { "gen": { "height": 805543 } } ], "vout": [ { "amount": 1314927372, "target": { "key": "8ebbea9b8d6f1565026274bcaa6317b04e6c6ae409187dcc3a89baee7e88c583" } } ], "extra": [ 1, 51, 126, 164, 52, 37, 161, 177, 231, 77, 176, 110, 74, 103, 214, 205, 232, 171, 34, 112, 111, 189, 171, 93, 166, 39, 21, 103, 31, 184, 14, 37, 37, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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