← previous blocknext block →recent activity
Analyzing
Block #90,835,393
17 transactions · 15 stateful · 2026-07-27 17:48:56 UTC
Parallelism
76/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,835,393 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f7c4f1…bba8
0x34b655…2a6f
4 touches
1 conflict
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0x7c46fde6…d6a0
0x34b655…2a6f
4 touches
1 conflict
0x7c977a16…8d39
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf18e87f5…6880
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
1 conflict on slot 0x27f7c4f114…d0bba8
Audit this contract →
← previous block·next block →recent activity