← previous blocknext block →recent activity
Analyzing
Block #90,540,721
8 transactions · 7 stateful · 2026-07-26 17:06:25 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,540,721 · 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
2w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d7d817f…6eee
0x34b655…2a6f
4 touches
1 conflict
0x19b4e3fd…3821
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0x46d86b6f…7c9c
0x065c9d…c394
2 touches
0 conflicts
0xa24428e2…73d6
0x065c9d…c394
2 touches
0 conflicts
0xb55f9222…b0b5
0x065c9d…c394
2 touches
0 conflicts
0xb90ddfba…af2a
0x065c9d…c394
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 0x0d7d817fd7…046eee
Audit this contract →
← previous block·next block →recent activity