← previous blocknext block →recent activity
Analyzing
Block #99,848,587
9 transactions · 9 stateful · 2026-08-28 08:17:20 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,848,587 · 9 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
1w02w03w14w25w16w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88bfd4c1…3190
0x34b655…2a6f
8 touches
6 conflicts
0xff462e14…a60c
0x34b655…2a6f
6 touches
3 conflicts
0x3c67d31e…3dbe
0x34b655…2a6f
6 touches
3 conflicts
0x30ef1feb…1308
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x88bfd4c1f6…b63190
Audit this contract →
← previous block·next block →recent activity