← previous blocknext block →recent activity
Analyzing
Block #108,103,694
18 transactions · 17 stateful · 2026-09-26 06:08:45 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,103,694 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x99714b34…f5c1
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xdd3b90f9…2413
0x34b655…2a6f
4 touches
1 conflict
0xe763a93c…e90b
0x34b655…2a6f
4 touches
1 conflict
0xeec2387a…2190
0x34b655…2a6f
4 touches
1 conflict
0xf0c299c4…0015
0x34b655…2a6f
4 touches
1 conflict
0x481db2dd…cc35
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity