← previous blocknext block →recent activity
Analyzing
Block #98,217,125
5 transactions · 5 stateful · 2026-08-22 14:31:23 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,217,125 · 5 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da1e393…5ef0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe22455da…1ce1
0x34b655…2a6f
4 touches
1 conflict
0x0c224cec…d438
0x34b655…2a6f
2 touches
0 conflicts
0x117d1e0c…e669
0x34b655…2a6f
2 touches
0 conflicts
0x3f8cfa83…9404
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x523de645…4f58
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 0x7da1e393d8…6b5ef0
Audit this contract →
← previous block·next block →recent activity