← previous blocknext block →recent activity
Analyzing
Block #108,451,545
17 transactions · 13 stateful · 2026-09-27 11:19:23 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,451,545 · 17 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
1w02w13w212w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70fa1dcc…3722
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0xa03c2a35…52e6
0x34b655…2a6f
8 touches
6 conflicts
0xcbc5eedb…b043
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc924ae2d…6941
0x34b655…2a6f
6 touches
3 conflicts
0x2504e58e…35a9
0x34b655…2a6f
4 touches
1 conflict
0xdc7b9eda…e616
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 0x70fa1dcc7a…663722
Audit this contract →
← previous block·next block →recent activity