← previous blocknext block →recent activity
Analyzing
Block #101,299,118
38 transactions · 26 stateful · 2026-09-02 10:01:25 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,299,118 · 38 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
1w02w17w08w09w011w018w020w121w222w123w127w228w329w331w236w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x615bc8cc…15d2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x1a4b4833…cf01
0x34b655…2a6f
4 touches
1 conflict
0x816924c8…bac9
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x615bc8cc79…5215d2
Audit this contract →
← previous block·next block →recent activity