← previous blocknext block →recent activity
Analyzing
Block #101,937,788
20 transactions · 17 stateful · 2026-09-04 15:36:25 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,937,788 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w49w210w314w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac27d4e9…fffc
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0x689c3def…2c57
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x93aaefce…5be5
0x34b655…2a6f
6 touches
3 conflicts
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0xb47d4bdd…6172
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xac27d4e99a…c3fffc
Audit this contract →
← previous block·next block →recent activity