← previous blocknext block →recent activity
Analyzing
Block #90,636,884
14 transactions · 12 stateful · 2026-07-27 01:10:11 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,636,884 · 14 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
5w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x312e4698…54c0
0x34b655…2a6f
6 touches
3 conflicts
0x0dab7a9b…c40e
0x34b655…2a6f
6 touches
3 conflicts
0xdc568d84…62d9
0x34b655…2a6f
6 touches
3 conflicts
0xa5908184…0fef
0x34b655…2a6f
6 touches
3 conflicts
0xc3656cd1…8269
0x34b655…2a6f
6 touches
3 conflicts
0xd9a771df…a27b
0x34b655…2a6f
6 touches
3 conflicts
0x803cd43b…b348
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity