← previous blocknext block →recent activity
Analyzing
Block #107,841,632
16 transactions · 14 stateful · 2026-09-25 08:09:45 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,841,632 · 16 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
1w02w17w18w29w310w411w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831a5ce7…722c
0x34b655…2a6f
10 touches
10 conflicts
0xbf9df290…b04d
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x508174fb…94d2
0x34b655…2a6f
10 touches
10 conflicts
0xc1da8f73…484c
0x34b655…2a6f
8 touches
6 conflicts
0x6e0f1dd3…db06
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
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
10 conflicts on slot 0x831a5ce7db…f8722c
Audit this contract →
← previous block·next block →recent activity