← previous blocknext block →recent activity
Analyzing
Block #91,781,092
17 transactions · 17 stateful · 2026-07-31 01:09:40 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,781,092 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w39w410w512w613w714w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0x691e3505…dd2f
0x34b655…2a6f
8 touches
6 conflicts
0x45ef9175…5ab2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x9b334941…fde0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5692e125…1727
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
6 conflicts on slot 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity