← previous blocknext block →recent activity
Analyzing
Block #107,813,423
34 transactions · 29 stateful · 2026-09-25 05:47:47 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,813,423 · 34 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
5w06w17w08w09w111w014w016w117w118w219w320w121w222w423w130w131w132w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
8 touches
6 conflicts
0x45a5f53c…e2da
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xa0cbbfcc…3133
0x34b655…2a6f
6 touches
3 conflicts
0x5fb32549…8586
0x34b655…2a6f
4 touches
1 conflict
0x6ce7d88f…31ea
0x34b655…2a6f
4 touches
1 conflict
0x1ae03ff2…30fd
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 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity