← previous blocknext block →recent activity
Analyzing
Block #99,708,928
14 transactions · 14 stateful · 2026-08-27 20:30:02 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,708,928 · 14 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
2w03w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57e5abc1…286f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x131543ca…09ba
0x34b655…2a6f
4 touches
1 conflict
0x931975c2…b7b3
0x34b655…2a6f
4 touches
1 conflict
0x0b3cfc56…2a4a
0x34b655…2a6f
2 touches
0 conflicts
0x272e5bd6…252d
0x34b655…2a6f
2 touches
0 conflicts
0x3f798539…99c4
0x34b655…2a6f
2 touches
0 conflicts
0x4067e36d…0134
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 0x57e5abc14c…cb286f
Audit this contract →
← previous block·next block →recent activity