← previous blocknext block →recent activity
Analyzing
Block #101,664,634
11 transactions · 11 stateful · 2026-09-03 16:40:28 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,664,634 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x0a0f80fc…e0d3
0x34b655…2a6f
4 touches
1 conflict
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x25331890…1f8d
0x34b655…2a6f
4 touches
1 conflict
0x420971ee…2a3c
0x34b655…2a6f
4 touches
1 conflict
0x445f6341…72d1
0x34b655…2a6f
4 touches
1 conflict
0x451a68c4…1004
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity