← previous blocknext block →recent activity
Analyzing
Block #92,444,735
9 transactions · 8 stateful · 2026-08-02 08:47:34 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,444,735 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x010f7612…7e01
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xce2f0b6e…0e05
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x36a76bd2…1fb0
0x34b655…2a6f
2 touches
0 conflicts
0x388633a0…86cd
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x010f761218…e27e01
Audit this contract →
← previous block·next block →recent activity