Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f1f65c174ee9a3b03902f963a6e288e126285381fe55887b363b6c520e6d609

Tx prefix hash: e95fd9e2477db86862fe8b7cb82642944fb57b96e33944307e6b496177fdc13a
Tx public key: b7ba2e9ad776be737055ea046155f1eedd9b3f02e5eca6948f32078a623a101a
Timestamp: 1580263258 Timestamp [UCT]: 2020-01-29 02:00:58 Age [y:d:h:m:s]: 05:028:01:25:18
Block: 54276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171671 RingCT/type: yes/0
Extra: 01b7ba2e9ad776be737055ea046155f1eedd9b3f02e5eca6948f32078a623a101a021100000001b221b3d1000000000000000000

1 output(s) for total of 405.659739730000 dcy

stealth address amount amount idx
00: 4875ecc5b38b2b25bf18e47a59b21d5301a45fcf38f2b27b053f02d62f3186b8 405.659739730000 100614 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": 54286, "vin": [ { "gen": { "height": 54276 } } ], "vout": [ { "amount": 405659739730, "target": { "key": "4875ecc5b38b2b25bf18e47a59b21d5301a45fcf38f2b27b053f02d62f3186b8" } } ], "extra": [ 1, 183, 186, 46, 154, 215, 118, 190, 115, 112, 85, 234, 4, 97, 85, 241, 238, 221, 155, 63, 2, 229, 236, 166, 148, 143, 50, 7, 138, 98, 58, 16, 26, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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