← previous blocknext block →recent activity
Analyzing
Block #91,969,474
16 transactions · 15 stateful · 2026-07-31 16:57:23 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,969,474 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w49w511w614w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x25ecf913…0ad8
0x34b655…2a6f
12 touches
15 conflicts
0x56153262…21ce
0x34b655…2a6f
12 touches
15 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x4954a433…820d
0x34b655…2a6f
6 touches
3 conflicts
0x6b7bba6c…0238
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity