← previous blocknext block →recent activity
Analyzing
Block #108,402,482
29 transactions · 26 stateful · 2026-09-27 07:12:25 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,402,482 · 29 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
1w02w13w212w317w022w424w526w628w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xd739490d…821e
0x34b655…2a6f
6 touches
3 conflicts
0x8643926f…a849
0x34b655…2a6f
6 touches
3 conflicts
0x032b200b…7eea
0xd32edf…ff58
5 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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity