← previous blocknext block →recent activity
Analyzing
Block #107,813,378
24 transactions · 18 stateful · 2026-09-25 05:47:33 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,378 · 24 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
9w010w111w212w313w414w515w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa23b9051…392f
0x34b655…2a6f
16 touches
28 conflicts
0x33d22247…6c39
0x34b655…2a6f
8 touches
6 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
6 touches
3 conflicts
0x2d0d6e63…0ffc
0x34b655…2a6f
6 touches
3 conflicts
0xbb96f8af…205f
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
28 conflicts on slot 0xa23b905120…88392f
Audit this contract →
← previous block·next block →recent activity