← previous blocknext block →recent activity
Analyzing
Block #108,113,148
16 transactions · 16 stateful · 2026-09-26 06:56:20 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,113,148 · 16 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
4w05w16w27w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x556beb43…e627
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x659933ab…e189
0x34b655…2a6f
6 touches
3 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
6 touches
3 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity