← previous blocknext block →recent activity
Analyzing
Block #91,975,189
18 transactions · 17 stateful · 2026-07-31 17:26:08 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,975,189 · 18 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
6w07w111w013w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c56751d…b5fd
0x34b655…2a6f
4 touches
1 conflict
0x71747f07…5ce1
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xabc824ec…e238
0x34b655…2a6f
3 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c1
0x1b6862…e19c
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 0x6c56751d0c…cfb5fd
Audit this contract →
← previous block·next block →recent activity