← previous blocknext block →recent activity
Analyzing
Block #107,816,634
28 transactions · 24 stateful · 2026-09-25 06:03:56 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,816,634 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w18w010w011w112w213w314w415w516w617w718w119w727w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x73bdda59…468d
0x34b655…2a6f
6 touches
3 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
6 touches
3 conflicts
0x3184c12e…b1b1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity