← previous blocknext block →recent activity
Analyzing
Block #107,838,399
18 transactions · 17 stateful · 2026-09-25 07:53:29 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,838,399 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w111w012w113w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d205b22…b005
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdee7ccf3…a686
0x34b655…2a6f
4 touches
1 conflict
0x0521620f…8f85
0x34b655…2a6f
4 touches
1 conflict
0xa2c4d203…05b6
0x34b655…2a6f
4 touches
1 conflict
0xe13ad55d…83b3
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
3 conflicts on slot 0x4d205b2287…c2b005
Audit this contract →
← previous block·next block →recent activity