← previous blocknext block →recent activity
Analyzing
Block #108,603,044
28 transactions · 26 stateful · 2026-09-28 00:02:11 UTC
Parallelism
86/100
Blocked
46%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,603,044 · 28 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
3w06w07w18w19w210w311w212w214w222w123w224w325w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x37b349cd…5f3b
0xd32edf…ff58
5 touches
3 conflicts
0x0d54fa3e…3b3c
0x34b655…2a6f
4 touches
1 conflict
0x0ecf5b65…88af
0x34b655…2a6f
4 touches
1 conflict
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x2684d6a4…3c39
0x34b655…2a6f
4 touches
1 conflict
0x280aaa58…1c52
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity