← previous blocknext block →recent activity
Analyzing
Block #108,496,378
26 transactions · 23 stateful · 2026-09-27 15:05:04 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,496,378 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w212w013w320w021w122w123w024w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88cf2d31…3d64
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc7259a45…01fa
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xddd9d39e…0c69
0x34b655…2a6f
4 touches
1 conflict
0x08cfec9d…7ef0
0x508254…98bd
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 0x88cf2d3101…3b3d64
Audit this contract →
← previous block·next block →recent activity