← previous blocknext block →recent activity
Analyzing
Block #91,209,642
21 transactions · 20 stateful · 2026-07-29 01:12:34 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,209,642 · 21 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
1w02w15w06w17w08w012w213w314w217w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
6 touches
3 conflicts
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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 0x7be3246e43…72f89f
Audit this contract →
← previous block·next block →recent activity