← previous blocknext block →recent activity
Analyzing
Block #107,786,186
19 transactions · 18 stateful · 2026-09-25 03:30:33 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,786,186 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w110w211w312w313w415w216w017w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2b9c600…de5f
0x34b655…2a6f
8 touches
6 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
6 touches
3 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
6 touches
3 conflicts
0x874cb67f…26e0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x06e35955…0bdd
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 0xa2b9c6008e…1ede5f
Audit this contract →
← previous block·next block →recent activity