← previous blocknext block →recent activity
Analyzing
Block #101,298,800
24 transactions · 23 stateful · 2026-09-02 09:59:49 UTC
Parallelism
92/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,298,800 · 24 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
5w06w07w18w09w012w014w119w020w121w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2528e717…2a22
0x34b655…2a6f
4 touches
1 conflict
0x678143da…dc6b
0x34b655…2a6f
4 touches
1 conflict
0x7151b1ad…4520
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf97b1ece…fbfa
0x34b655…2a6f
4 touches
1 conflict
0xf9ffe85c…1d4a
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 0x2528e7175c…302a22
Audit this contract →
← previous block·next block →recent activity