← previous blocknext block →recent activity
Analyzing
Block #108,103,273
15 transactions · 15 stateful · 2026-09-26 06:06:38 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,103,273 · 15 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
1w06w07w18w19w212w013w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7063105…100b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x95f1f7e6…9cdd
0x34b655…2a6f
6 touches
3 conflicts
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x625c4ed4…16aa
0x34b655…2a6f
4 touches
1 conflict
0x69ba9af6…f96e
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 0xf70631053c…4e100b
Audit this contract →
← previous block·next block →recent activity