← previous blocknext block →recent activity
Analyzing
Block #106,569,926
41 transactions · 38 stateful · 2026-09-20 21:25:26 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
1.02
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,569,926 · 41 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w17w211w112w213w318w421w222w323w427w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x28cf9680…8550
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0x3efc4ea8…a302
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x925400bb…a253
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
10 conflicts on slot 0x310a7246ab…012dcb
Audit this contract →
← previous block·next block →recent activity