← previous blocknext block →recent activity
Analyzing
Block #90,682,473
8 transactions · 6 stateful · 2026-07-27 04:59:32 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,682,473 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x88f81e37…b9dd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x085e35d2…8d20
0x34b655…2a6f
2 touches
0 conflicts
0x5c490ba5…f4a2
0x34b655…2a6f
2 touches
0 conflicts
0x80398c66…f3cc
0x34b655…2a6f
2 touches
0 conflicts
0x84ad80c8…6fa1
0x34b655…2a6f
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity