← previous blocknext block →recent activity
Analyzing
Block #101,322,083
22 transactions · 19 stateful · 2026-09-02 11:56:58 UTC
Parallelism
91/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,322,083 · 22 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
1w02w14w06w19w017w018w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x932a9590…0b19
0x34b655…2a6f
4 touches
1 conflict
0xa742cc4c…dd0f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x2e1f5171…ad2d
0x34b655…2a6f
2 touches
0 conflicts
0xd4230a60…bd13
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 0x932a9590fe…330b19
Audit this contract →
← previous block·next block →recent activity