← previous blocknext block →recent activity
Analyzing
Block #106,190,461
24 transactions · 22 stateful · 2026-09-19 13:35:34 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
2.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,190,461 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w212w213w314w415w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb935707a…140f
0x34b655…2a6f
16 touches
28 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
8 touches
6 conflicts
0x6b23a89e…1057
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
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
28 conflicts on slot 0xb935707a6d…a1140f
Audit this contract →
← previous block·next block →recent activity