← previous blocknext block →recent activity
Analyzing
Block #98,386,194
13 transactions · 11 stateful · 2026-08-23 04:41:58 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,386,194 · 13 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
1w04w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b4267f7…96c0
0x34b655…2a6f
4 touches
1 conflict
0xfb4fd6ce…262e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2464aa51…9766
0x34b655…2a6f
2 touches
0 conflicts
0x272dc9b8…1b58
0x34b655…2a6f
2 touches
0 conflicts
0x2beef0db…072d
0x34b655…2a6f
2 touches
0 conflicts
0x5fde4971…aac9
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
1 conflict on slot 0x0b4267f73f…2796c0
Audit this contract →
← previous block·next block →recent activity