← previous blocknext block →recent activity
Analyzing
Block #91,210,523
19 transactions · 17 stateful · 2026-07-29 01:17:00 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,210,523 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1526b11f…8b21
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2c66ecd1…f41d
0x34b655…2a6f
6 touches
3 conflicts
0x4aa7b77c…4f57
0x34b655…2a6f
4 touches
1 conflict
0x4ecbd5bb…f290
0x34b655…2a6f
4 touches
1 conflict
0x5d041208…74ae
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
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 0x1526b11fec…5a8b21
Audit this contract →
← previous block·next block →recent activity