← previous blocknext block →recent activity
Analyzing
Block #106,198,115
24 transactions · 21 stateful · 2026-09-19 14:14:05 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,198,115 · 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
3w04w15w06w07w18w29w310w011w112w113w218w019w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
4 touches
1 conflict
0x68292fe7…d918
0x34b655…2a6f
4 touches
1 conflict
0x74fa9cc0…c570
0x34b655…2a6f
4 touches
1 conflict
0x88c076d4…6c76
0x34b655…2a6f
4 touches
1 conflict
0x95853c58…5ec3
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: 0xf5b5f7f8…a36d70
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity