← previous blocknext block →recent activity
Analyzing
Block #98,273,300
35 transactions · 24 stateful · 2026-08-22 19:13:58 UTC
Parallelism
91/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,273,300 · 35 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w121w022w124w228w231w032w134w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6713b018…05f3
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x25da5e59…fee6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
5 touches
3 conflicts
0x80884f59…ac94
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x6713b0185b…1305f3
Audit this contract →
← previous block·next block →recent activity