← previous blocknext block →recent activity
Analyzing
Block #108,972,016
31 transactions · 22 stateful · 2026-09-29 07:04:10 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,972,016 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w010w115w016w117w218w319w421w524w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4bcfcf8…2ad1
0x34b655…2a6f
8 touches
6 conflicts
0x3265b7ee…d0f4
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xc1da8f73…484c
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0x30f54ecb…ab9a
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xc4bcfcf819…c32ad1
Audit this contract →
← previous block·next block →recent activity