← previous blocknext block →recent activity
Analyzing
Block #101,308,280
19 transactions · 18 stateful · 2026-09-02 10:47:32 UTC
Parallelism
84/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,308,280 · 19 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
6w013w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b80986d…b57a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2ad2f4bc…1800
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0xe57aedd9…c61b
0x5afd3e…7620
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 0x8b80986dd6…77b57a
Audit this contract →
← previous block·next block →recent activity