← previous blocknext block →recent activity
Analyzing
Block #101,323,960
36 transactions · 30 stateful · 2026-09-02 12:06:25 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,323,960 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w18w09w010w111w112w013w118w122w223w224w325w326w433w034w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678143da…dc6b
0x34b655…2a6f
10 touches
10 conflicts
0xb5811949…acae
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
0x84630401…6ca5
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
10 conflicts on slot 0x678143daa0…40dc6b
Audit this contract →
← previous block·next block →recent activity