← previous blocknext block →recent activity
Analyzing
Block #108,493,940
22 transactions · 20 stateful · 2026-09-27 14:52:47 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,493,940 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w113w214w315w416w117w518w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e7c336…91ff
0x34b655…2a6f
8 touches
6 conflicts
0xe8f46f4d…dbd5
0x34b655…2a6f
8 touches
6 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x0f28fb99…3d2d
0x1b6862…e19c
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 0xe2e7c33695…ce91ff
Audit this contract →
← previous block·next block →recent activity