← previous blocknext block →recent activity
Analyzing
Block #108,503,725
20 transactions · 18 stateful · 2026-09-27 15:42:03 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,503,725 · 20 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
2w08w09w011w112w213w114w315w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1448207…452d
0x34b655…2a6f
8 touches
6 conflicts
0xe743f7a1…a125
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x88cf2d31…3d64
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 0xd144820738…06452d
Audit this contract →
← previous block·next block →recent activity