← previous blocknext block →recent activity
Analyzing
Block #106,330,308
12 transactions · 11 stateful · 2026-09-20 01:19:26 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,330,308 · 12 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
1w02w03w06w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbc417c5e…4f97
0x34b655…2a6f
6 touches
3 conflicts
0x2631b5d1…886b
0x34b655…2a6f
6 touches
3 conflicts
0xfac38cc8…fb9d
0x34b655…2a6f
4 touches
1 conflict
0x39561c15…c70f
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity