← previous blocknext block →recent activity
Analyzing
Block #98,726,436
12 transactions · 11 stateful · 2026-08-24 09:50:00 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,726,436 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x641aed07…bcb9
0x34b655…2a6f
4 touches
1 conflict
0xf6c2bee0…a1f1
0x34b655…2a6f
4 touches
1 conflict
0x7662d077…c6bc
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
2 touches
0 conflicts
0x627738d1…db02
0x34b655…2a6f
2 touches
0 conflicts
0x99de109c…1712
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xd08f3d06…d168
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 0x641aed075a…00bcb9
Audit this contract →
← previous block·next block →recent activity