← previous blocknext block →recent activity
Analyzing
Block #108,566,117
27 transactions · 23 stateful · 2026-09-27 20:56:19 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,566,117 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w08w09w113w016w217w318w319w422w425w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb62767a7…89fe
0x34b655…2a6f
8 touches
6 conflicts
0x4f251bf6…fc23
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x660b6e4f…3d72
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
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 0xb62767a76d…b789fe
Audit this contract →
← previous block·next block →recent activity