← previous blocknext block →recent activity
Analyzing
Block #101,303,017
35 transactions · 26 stateful · 2026-09-02 10:21:02 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.14
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,303,017 · 35 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
5w011w012w120w121w222w331w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf620f2c4…773e
0x34b655…2a6f
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0xf620f2c468…1d773e
Audit this contract →
← previous block·next block →recent activity