← previous blocknext block →recent activity
Analyzing
Block #98,415,112
16 transactions · 14 stateful · 2026-08-23 07:07:28 UTC
Parallelism
75/100
Blocked
21%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,415,112 · 16 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
5w06w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ec1667a…81f3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e8f1bea…875b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x45f9b8a1…5064
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
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
3 conflicts on slot 0x3ec1667ab4…e081f3
Audit this contract →
← previous block·next block →recent activity