← previous blocknext block →recent activity
Analyzing
Block #101,248,707
14 transactions · 13 stateful · 2026-09-02 05:47:47 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,248,707 · 14 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
5w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6f96e4d…e2f5
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x5f504062…50f4
0x34b655…2a6f
4 touches
1 conflict
0x93f1d5e2…9290
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
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 0xe6f96e4dd8…fbe2f5
Audit this contract →
← previous block·next block →recent activity