← previous blocknext block →recent activity
Analyzing
Block #108,448,556
12 transactions · 8 stateful · 2026-09-27 11:04:21 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,448,556 · 12 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518b8dce…6d60
0x34b655…2a6f
4 touches
1 conflict
0x6103240d…5df5
0x34b655…2a6f
4 touches
1 conflict
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0xdabae01b…82be
0x34b655…2a6f
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x54d16ba4…13a2
0x34b655…2a6f
2 touches
0 conflicts
0x7fe41146…1f9f
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 0x518b8dce2e…7e6d60
Audit this contract →
← previous block·next block →recent activity