← previous blocknext block →recent activity
Analyzing
Block #101,303,360
20 transactions · 19 stateful · 2026-09-02 10:22:46 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,303,360 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w110w112w213w316w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f5f775…010b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x0e73da68…dcd5
0x34b655…2a6f
4 touches
1 conflict
0x1a356d76…6c74
0x34b655…2a6f
4 touches
1 conflict
0x2528e717…2a22
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
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
3 conflicts on slot 0xb5f5f77567…50010b
Audit this contract →
← previous block·next block →recent activity