← previous blocknext block →recent activity
Analyzing
Block #91,398,589
18 transactions · 17 stateful · 2026-07-29 17:04:10 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,398,589 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w010w011w113w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x74ae383e…8658
0x8d1565…6723
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0xe33999aa…8e37
0x8d1565…6723
8 touches
6 conflicts
0xb6fd44b1…dbf6
0x8d1565…6723
8 touches
6 conflicts
0xe08efbe7…1658
0x227add…4c03
7 touches
6 conflicts
0x265eab82…fafa
0x336ed4…c59c
7 touches
6 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity