← previous blocknext block →recent activity
Analyzing
Block #101,324,488
34 transactions · 26 stateful · 2026-09-02 12:09:04 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,324,488 · 34 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
1w03w04w15w28w09w114w017w121w223w024w325w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff324643…41db
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x52a23ecb…8f25
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3b
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3c
0x34b655…2a6f
4 touches
1 conflict
0xaca60768…7272
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
3 conflicts on slot 0xff3246434a…9541db
Audit this contract →
← previous block·next block →recent activity