← previous blocknext block →recent activity
Analyzing
Block #98,744,841
16 transactions · 11 stateful · 2026-08-24 11:22:35 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,744,841 · 16 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
1w03w07w18w010w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f5119b3…3e43
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x71480e0a…7d12
0x34b655…2a6f
4 touches
1 conflict
0x80fbbc84…94c9
0x34b655…2a6f
4 touches
1 conflict
0x99b05878…1572
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
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
1 conflict on slot 0x1f5119b312…6f3e43
Audit this contract →
← previous block·next block →recent activity