← previous blocknext block →recent activity
Analyzing
Block #101,303,086
13 transactions · 11 stateful · 2026-09-02 10:21:23 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,303,086 · 13 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
3w04w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5753e7d3…4676
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x2528e717…2a22
0x34b655…2a6f
4 touches
1 conflict
0x615bc8cc…15d2
0x34b655…2a6f
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0x97d2b812…af96
0x34b655…2a6f
4 touches
1 conflict
0x4392cbcd…6a92
0x34b655…2a6f
2 touches
0 conflicts
0x5c765dbc…b986
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 0x5753e7d3bb…524676
Audit this contract →
← previous block·next block →recent activity