← previous blocknext block →recent activity
Analyzing
Block #101,307,824
21 transactions · 18 stateful · 2026-09-02 10:45:14 UTC
Parallelism
81/100
Blocked
22%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,307,824 · 21 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
2w03w113w216w017w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7f9622bd…ef05
0xa6afd3…d132
4 touches
1 conflict
0x901b2a81…7af9
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
2 touches
0 conflicts
0x5eb6a5ed…acf8
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity