← previous blocknext block →recent activity
Analyzing
Block #91,558,588
16 transactions · 14 stateful · 2026-07-30 06:30:23 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,558,588 · 16 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
1w04w09w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x45afe05e…1607
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x0d9c5df5…66d4
0x34b655…2a6f
2 touches
0 conflicts
0x1683a436…2c42
0x34b655…2a6f
2 touches
0 conflicts
0x3dc9f1ae…c0fc
0x34b655…2a6f
2 touches
0 conflicts
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 0xa47b776601…7cee6e
Audit this contract →
← previous block·next block →recent activity