← previous blocknext block →recent activity
Analyzing
Block #106,385,602
15 transactions · 15 stateful · 2026-09-20 05:57:43 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,385,602 · 15 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
1w05w16w27w38w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b1b0b25…173b
0x5be4ee…673f
9 touches
10 conflicts
0x8b1b0b25…1749
0x5be4ee…673f
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x1e665745…8517
0x34b655…2a6f
6 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
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: 0x5be4ee8b…b7673f
10 conflicts on slot 0x8b1b0b2537…d8173b
Audit this contract →
← previous block·next block →recent activity