← previous blocknext block →recent activity
Analyzing
Block #106,569,718
14 transactions · 14 stateful · 2026-09-20 21:24:23 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,569,718 · 14 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
4w05w16w27w08w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87ac6e5b…5198
0x34b655…2a6f
8 touches
6 conflicts
0xe7826b5b…166a
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360d
0x34b655…2a6f
4 touches
1 conflict
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0xac0b4a08…faae
0x34b655…2a6f
4 touches
1 conflict
0xad401fc6…8648
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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 0x87ac6e5b1c…c75198
Audit this contract →
← previous block·next block →recent activity