← previous blocknext block →recent activity
Analyzing
Block #98,676,663
13 transactions · 12 stateful · 2026-08-24 05:35:56 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,676,663 · 13 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
2w03w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd1f60fdc…738e
0x34b655…2a6f
3 touches
1 conflict
0x0299d0eb…ce68
0x34b655…2a6f
2 touches
0 conflicts
0x21636513…a198
0x34b655…2a6f
2 touches
0 conflicts
0x21869930…2d1b
0x34b655…2a6f
2 touches
0 conflicts
0x27b6010e…e4aa
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity