← previous blocknext block →recent activity
Analyzing
Block #101,323,397
12 transactions · 11 stateful · 2026-09-02 12:03:35 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,323,397 · 12 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
6w07w18w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0x5ab4d7c5…c0f5
0x34b655…2a6f
4 touches
1 conflict
0x678143da…dc6b
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x24b08f9c98…6ae594
Audit this contract →
← previous block·next block →recent activity