← previous blocknext block →recent activity
Analyzing
Block #106,235,793
24 transactions · 23 stateful · 2026-09-19 17:23:49 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,235,793 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w09w110w311w415w517w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x8328c4b3…7a33
0x34b655…2a6f
8 touches
6 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x6887ee0c…9794
0x34b655…2a6f
6 touches
3 conflicts
0x8dff44f3…cd7c
0x34b655…2a6f
6 touches
3 conflicts
0x15e313f3…9aa1
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 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity