← previous blocknext block →recent activity
Analyzing
Block #108,010,189
18 transactions · 18 stateful · 2026-09-25 22:18:14 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,010,189 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79d01a4…5ba8
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x21d7582a…4439
0x34b655…2a6f
2 touches
0 conflicts
0xd5f675a8…9d81
0x34b655…2a6f
2 touches
0 conflicts
0xe2513f8c…b81d
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xf79d01a454…3f5ba8
Audit this contract →
← previous block·next block →recent activity