← previous blocknext block →recent activity
Analyzing
Block #108,941,977
12 transactions · 11 stateful · 2026-09-29 04:32:00 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,941,977 · 12 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
3w04w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4c059d8…185d
0x34b655…2a6f
8 touches
6 conflicts
0x07161dec…6065
0x34b655…2a6f
8 touches
6 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0xc6d64905…a59b
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x99ecae25…abb9
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x463017a2…d628
0x851145…3f07
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 0xc4c059d8f6…bf185d
Audit this contract →
← previous block·next block →recent activity