← previous blocknext block →recent activity
Analyzing
Block #107,848,272
19 transactions · 18 stateful · 2026-09-25 08:43:11 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,848,272 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x232b0b19…d946
0x34b655…2a6f
12 touches
15 conflicts
0xd344088c…806f
0x34b655…2a6f
12 touches
15 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
8 touches
6 conflicts
0x70335443…ff8e
0x34b655…2a6f
6 touches
3 conflicts
0xfa2794a8…40de
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
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
15 conflicts on slot 0x232b0b19e0…d1d946
Audit this contract →
← previous block·next block →recent activity