← previous blocknext block →recent activity
Analyzing
Block #107,278,553
25 transactions · 24 stateful · 2026-09-23 08:53:32 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,278,553 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9c1bb1a…45de
0x34b655…2a6f
16 touches
28 conflicts
0xf414f665…e810
0x34b655…2a6f
16 touches
28 conflicts
0xee8237bd…46ad
0x34b655…2a6f
10 touches
10 conflicts
0x469dac8d…3411
0x34b655…2a6f
10 touches
10 conflicts
0x34eb3605…9253
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xeb7dd16a…e54b
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
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
28 conflicts on slot 0xd9c1bb1aeb…e145de
Audit this contract →
← previous block·next block →recent activity