← previous blocknext block →recent activity
Analyzing
Block #108,657,583
16 transactions · 16 stateful · 2026-09-28 04:36:51 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,657,583 · 16 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
1w02w15w26w17w28w39w412w013w114w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91f9f021…0820
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x68f7aaba…88df
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
6 touches
3 conflicts
0xc2d7da7d…a21f
0xd32edf…ff58
5 touches
3 conflicts
0x43e3decb…be40
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 0x91f9f0213b…9c0820
Audit this contract →
← previous block·next block →recent activity