← previous blocknext block →recent activity
Analyzing
Block #108,533,064
24 transactions · 21 stateful · 2026-09-27 18:09:43 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,533,064 · 24 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
2w05w06w17w19w010w111w212w318w019w120w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x1e393384…1d24
0x34b655…2a6f
10 touches
10 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0x75f928fc…0465
0x34b655…2a6f
8 touches
6 conflicts
0xb06e76e0…51cb
0x34b655…2a6f
8 touches
6 conflicts
0xc1a4c088…e828
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
10 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity