Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2e9ce08e69e9774b03b88a93f5de2bf12e49472b887d73065c922c5dd9619a1

Tx prefix hash: acb1aa3fcd395feff552b67a91539b7670e3d3e14158c598fd392efa19650bf9
Tx public key: e0bc0c1b4303197970ef4b8b914eff556d55b9366c75f6daf4bf866ae2de0347
Timestamp: 1574725139 Timestamp [UCT]: 2019-11-25 23:38:59 Age [y:d:h:m:s]: 05:044:14:04:18
Block: 17513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174689 RingCT/type: yes/0
Extra: 01e0bc0c1b4303197970ef4b8b914eff556d55b9366c75f6daf4bf866ae2de034702110000000a21bf71c4000000000000000000

1 output(s) for total of 536.998461541000 dcy

stealth address amount amount idx
00: a891094033626fecc38e8e4e4970225da3313bec4d4d77d56b1e2a9b7149588f 536.998461541000 25547 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": 17523, "vin": [ { "gen": { "height": 17513 } } ], "vout": [ { "amount": 536998461541, "target": { "key": "a891094033626fecc38e8e4e4970225da3313bec4d4d77d56b1e2a9b7149588f" } } ], "extra": [ 1, 224, 188, 12, 27, 67, 3, 25, 121, 112, 239, 75, 139, 145, 78, 255, 85, 109, 85, 185, 54, 108, 117, 246, 218, 244, 191, 134, 106, 226, 222, 3, 71, 2, 17, 0, 0, 0, 10, 33, 191, 113, 196, 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