← previous blocknext block →recent activity
Analyzing
Block #107,814,341
14 transactions · 13 stateful · 2026-09-25 05:52:24 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,814,341 · 14 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
1w02w16w07w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
12 touches
15 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0xd7fff095…7a34
0x34b655…2a6f
8 touches
6 conflicts
0xaa645624…7ea9
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xdc16b418…2f5d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity