← previous blocknext block →recent activity
Analyzing
Block #101,501,193
10 transactions · 9 stateful · 2026-09-03 02:58:15 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,501,193 · 10 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
1w02w13w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18f83499…f772
0x34b655…2a6f
4 touches
1 conflict
0x2247defb…89aa
0x34b655…2a6f
4 touches
1 conflict
0x4778019e…cac4
0x34b655…2a6f
4 touches
1 conflict
0x58c745f6…fe5d
0x34b655…2a6f
4 touches
1 conflict
0x8b113392…6b42
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xdf44437b…d261
0x34b655…2a6f
4 touches
1 conflict
0x04668899…39eb
0xd32edf…ff58
3 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 0x18f83499ab…60f772
Audit this contract →
← previous block·next block →recent activity