← previous blocknext block →recent activity
Analyzing
Block #108,501,318
17 transactions · 17 stateful · 2026-09-27 15:29:56 UTC
Parallelism
59/100
Blocked
59%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,501,318 · 17 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
1w02w13w24w38w09w110w211w312w413w514w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xc2aacf41…5501
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity