Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637772776fb891c0232f6ccbc316cd7275ae00c256513a0592ce01cba651a3a0

Tx prefix hash: b75fe424e3c22e63bf1cc22a00add848fd24df8a3a1e553f566bf0811c75a1e7
Tx public key: 6ee136235842ed1658f3c9f2a8f8ebaa0a46c74a5b25bc4eda09c73bd1d9740c
Timestamp: 1574900407 Timestamp [UCT]: 2019-11-28 00:20:07 Age [y:d:h:m:s]: 04:355:18:30:46
Block: 18745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136393 RingCT/type: yes/0
Extra: 016ee136235842ed1658f3c9f2a8f8ebaa0a46c74a5b25bc4eda09c73bd1d9740c02110000001f5d286194000000000000000000

1 output(s) for total of 531.974619061000 dcy

stealth address amount amount idx
00: 3f91c4770a95711a0618e70353a4d37ef2df9bc5b82ea4813b245b87b68c9cbe 531.974619061000 29142 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": 18755, "vin": [ { "gen": { "height": 18745 } } ], "vout": [ { "amount": 531974619061, "target": { "key": "3f91c4770a95711a0618e70353a4d37ef2df9bc5b82ea4813b245b87b68c9cbe" } } ], "extra": [ 1, 110, 225, 54, 35, 88, 66, 237, 22, 88, 243, 201, 242, 168, 248, 235, 170, 10, 70, 199, 74, 91, 37, 188, 78, 218, 9, 199, 59, 209, 217, 116, 12, 2, 17, 0, 0, 0, 31, 93, 40, 97, 148, 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