← previous blocknext block →recent activity
Analyzing
Block #108,396,301
14 transactions · 14 stateful · 2026-09-27 06:41:19 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,396,301 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w19w110w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8b7e65f…2816
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0xfdf1a05b…1e18
0x34b655…2a6f
4 touches
1 conflict
0x1794fb8c…a91a
0x34b655…2a6f
4 touches
1 conflict
0x191cc704…89f4
0x34b655…2a6f
4 touches
1 conflict
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0xf8b7e65f29…052816
Audit this contract →
← previous block·next block →recent activity