← previous blocknext block →recent activity
Analyzing
Block #106,198,036
30 transactions · 26 stateful · 2026-09-19 14:13:42 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,198,036 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w29w312w113w216w017w120w021w124w127w128w029w3
- 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
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x88c076d4…6c76
0x34b655…2a6f
4 touches
1 conflict
0x899a95b3…c38a
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