Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcd68338490244c963731e681a43c739e43de6d418e4da9ed3e9b3bd49389438

Tx prefix hash: fbbd731e4199868f5550e2f91439702eba84b28eb3dce2ab558fa05fe154473a
Tx public key: 65849102c1ab09aae5f89a334a5906e2b144631ae38026c4a0f934f5f69c3d79
Timestamp: 1574652461 Timestamp [UCT]: 2019-11-25 03:27:41 Age [y:d:h:m:s]: 05:343:13:10:45
Block: 16864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1385901 RingCT/type: yes/0
Extra: 0165849102c1ab09aae5f89a334a5906e2b144631ae38026c4a0f934f5f69c3d7902110000001d0b4dd45a000000000000000000

1 output(s) for total of 539.664001001000 dcy

stealth address amount amount idx
00: dad8999601526dd36f1d5ed48317a37a727b8f6b6d28e35375222ec7762f8920 539.664001001000 23948 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": 16874, "vin": [ { "gen": { "height": 16864 } } ], "vout": [ { "amount": 539664001001, "target": { "key": "dad8999601526dd36f1d5ed48317a37a727b8f6b6d28e35375222ec7762f8920" } } ], "extra": [ 1, 101, 132, 145, 2, 193, 171, 9, 170, 229, 248, 154, 51, 74, 89, 6, 226, 177, 68, 99, 26, 227, 128, 38, 196, 160, 249, 52, 245, 246, 156, 61, 121, 2, 17, 0, 0, 0, 29, 11, 77, 212, 90, 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