← previous blocknext block →recent activity
Analyzing
Block #107,794,827
24 transactions · 18 stateful · 2026-09-25 04:14:12 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,794,827 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w38w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6e0f6282…32cf
0x40c49f…2af0
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x3ff9db2e…22f6
0x34b655…2a6f
6 touches
3 conflicts
0x4df2af73…275a
0xd18b7e…414b
4 touches
1 conflict
0x0b61cc1d…4f81
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity