← previous blocknext block →recent activity
Analyzing
Block #101,325,629
16 transactions · 14 stateful · 2026-09-02 12:14:49 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,325,629 · 16 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
2w07w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12e7c471…901c
0x34b655…2a6f
4 touches
1 conflict
0x793c1a69…b8d1
0x34b655…2a6f
4 touches
1 conflict
0xe8f5e33f…719c
0x34b655…2a6f
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x1653f4fe…be5f
0x34b655…2a6f
2 touches
0 conflicts
0x1c255088…e409
0x34b655…2a6f
2 touches
0 conflicts
0x2a719b1d…365f
0x34b655…2a6f
2 touches
0 conflicts
0x2e1f5171…ad2d
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 0x12e7c471ad…22901c
Audit this contract →
← previous block·next block →recent activity