← previous blocknext block →recent activity
Analyzing
Block #107,849,136
20 transactions · 19 stateful · 2026-09-25 08:47:32 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,849,136 · 20 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
6w08w09w110w211w312w413w514w615w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x54e6d2a8…ec22
0x34b655…2a6f
6 touches
3 conflicts
0xa489b3e9…865c
0x34b655…2a6f
6 touches
3 conflicts
0xf75c3a6b…0568
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity