← previous blocknext block →recent activity
Analyzing
Block #101,306,800
21 transactions · 20 stateful · 2026-09-02 10:40:05 UTC
Parallelism
90/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,306,800 · 21 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
1w02w15w06w07w18w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf496f80c…d5c8
0x34b655…2a6f
4 touches
1 conflict
0x02bfdbf9…6514
0x34b655…2a6f
4 touches
1 conflict
0x63e367c9…b363
0x754704…b603
2 touches
0 conflicts
0x643fa4aa…a822
0x754704…b603
2 touches
0 conflicts
0xc98b6062…73eb
0x754704…b603
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity