← previous blocknext block →recent activity
Analyzing
Block #108,463,106
16 transactions · 15 stateful · 2026-09-27 12:17:34 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,463,106 · 16 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
1w02w17w08w19w210w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0x1fb6e47f…b99a
0x34b655…2a6f
8 touches
6 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0xdad13823…6798
0x37db7f…ec7b
8 touches
6 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
8 touches
6 conflicts
0x12e77486…ec2b
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity