← previous blocknext block →recent activity
Analyzing
Block #101,662,279
21 transactions · 18 stateful · 2026-09-03 16:28:37 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,662,279 · 21 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
3w04w16w27w38w49w510w011w112w215w416w317w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x17d87f0d…bfc5
0x34b655…2a6f
6 touches
3 conflicts
0x73cb3341…db65
0x34b655…2a6f
6 touches
3 conflicts
0xb9e03d71…72da
0x34b655…2a6f
6 touches
3 conflicts
0x4b58de6a…d67a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity