Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07bf6826621ca69cd5b708f04ac1f55e73aa2b1a43204bc9f31e1805798a86c

Tx prefix hash: 2a38a73810e86bc36de35ca2b6fcb9772357b863fb29807169a5d30a68453fcc
Tx public key: e3a7d3a2a110d23345f30c968b2a2fd1c3a805e11a6c3ae24232aff090845779
Timestamp: 1648839238 Timestamp [UCT]: 2022-04-01 18:53:58 Age [y:d:h:m:s]: 03:213:05:36:25
Block: 471107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 930467 RingCT/type: yes/0
Extra: 01e3a7d3a2a110d23345f30c968b2a2fd1c3a805e11a6c3ae24232aff090845779021100000002a8c141c5000000000000000000

1 output(s) for total of 16.866586232000 dcy

stealth address amount amount idx
00: de030281bb543436026eed4cfc27f6b74f932f776f0733a5b472936da2049900 16.866586232000 890381 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": 471117, "vin": [ { "gen": { "height": 471107 } } ], "vout": [ { "amount": 16866586232, "target": { "key": "de030281bb543436026eed4cfc27f6b74f932f776f0733a5b472936da2049900" } } ], "extra": [ 1, 227, 167, 211, 162, 161, 16, 210, 51, 69, 243, 12, 150, 139, 42, 47, 209, 195, 168, 5, 225, 26, 108, 58, 226, 66, 50, 175, 240, 144, 132, 87, 121, 2, 17, 0, 0, 0, 2, 168, 193, 65, 197, 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