← previous blocknext block →recent activity
Analyzing
Block #107,824,002
8 transactions · 8 stateful · 2026-09-25 06:41:01 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,824,002 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ba83b5…d0a8
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x3d24f8e0…5ab3
0x34b655…2a6f
4 touches
1 conflict
0x6dac76e3…04c9
0x34b655…2a6f
4 touches
1 conflict
0x9f7f164a…cd94
0x1c8a33…d316
2 touches
0 conflicts
0x1ddcfe3f…9a06
0x754704…b603
2 touches
0 conflicts
0x5943058d…92ee
0x754704…b603
2 touches
0 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
1 conflict on slot 0xa7ba83b5e1…e4d0a8
Audit this contract →
← previous block·next block →recent activity