← previous blocknext block →recent activity
Analyzing
Block #101,017,325
15 transactions · 15 stateful · 2026-09-01 10:23:26 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,017,325 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w111w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0xc824cf63…7ced
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
2 touches
0 conflicts
0x9ad325f5…cc43
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
1 conflict on slot 0x1db5837f6b…d01264
Audit this contract →
← previous block·next block →recent activity