← previous blocknext block →recent activity
Analyzing
Block #107,839,446
21 transactions · 21 stateful · 2026-09-25 07:58:45 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,839,446 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w08w19w110w112w213w314w415w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb195cffa…8098
0x34b655…2a6f
12 touches
15 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0xabce9cc8…3c73
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
6 touches
3 conflicts
0x5bb766da…3cf5
0xd32edf…ff58
5 touches
3 conflicts
0xaa6eea57…276d
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
15 conflicts on slot 0xb195cffa54…368098
Audit this contract →
← previous block·next block →recent activity