← previous blocknext block →recent activity
Analyzing
Block #90,456,921
6 transactions · 6 stateful · 2026-07-26 10:04:51 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,456,921 · 6 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
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xf9ea536a…818e
0x34b655…2a6f
4 touches
1 conflict
0x00c89f9d…f5bf
0x34b655…2a6f
2 touches
0 conflicts
0x05209750…eda3
0x34b655…2a6f
2 touches
0 conflicts
0x0bce8fb9…edb6
0x34b655…2a6f
2 touches
0 conflicts
0x11f2aded…153a
0x34b655…2a6f
2 touches
0 conflicts
0x13a6cdf5…5ebf
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 0xa07e7b13f3…e77513
Audit this contract →
← previous block·next block →recent activity