← previous blocknext block →recent activity
Analyzing
Block #107,824,162
32 transactions · 24 stateful · 2026-09-25 06:41:50 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,824,162 · 32 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
2w03w14w05w16w07w18w212w013w114w215w016w317w418w519w131w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x02ee3e98…d4fc
0x34b655…2a6f
4 touches
1 conflict
0x032badcf…a357
0x34b655…2a6f
4 touches
1 conflict
0x1ab8e26f…8ae8
0x34b655…2a6f
4 touches
1 conflict
0x43c28d17…a007
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity