← previous blocknext block →recent activity
Analyzing
Block #108,103,713
11 transactions · 11 stateful · 2026-09-26 06:08:50 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,103,713 · 11 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
4w05w16w17w29w010w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99714b34…f5c1
0x34b655…2a6f
6 touches
3 conflicts
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0xc49bec63…83d4
0x34b655…2a6f
4 touches
1 conflict
0xcb431cf5…3cb4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf0c299c4…0015
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
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
3 conflicts on slot 0x99714b3461…02f5c1
Audit this contract →
← previous block·next block →recent activity