← previous blocknext block →recent activity
Analyzing
Block #90,878,437
13 transactions · 12 stateful · 2026-07-27 21:25:30 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,878,437 · 13 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00d973f3…c791
0x34b655…2a6f
2 touches
0 conflicts
0x05c405e8…1590
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cb
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cc
0x34b655…2a6f
2 touches
0 conflicts
0x7a2c83a3…a29a
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 0xef3f5637ee…e7f47c
Audit this contract →
← previous block·next block →recent activity