← previous blocknext block →recent activity
Analyzing
Block #107,823,045
20 transactions · 19 stateful · 2026-09-25 06:36:12 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,823,045 · 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
4w09w010w111w212w313w414w515w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
10 touches
10 conflicts
0xbf496a61…9dcc
0x34b655…2a6f
8 touches
6 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x1abfd3ae…2999
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity