← previous blocknext block →recent activity
Analyzing
Block #90,460,590
21 transactions · 17 stateful · 2026-07-26 10:23:18 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,460,590 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w010w216w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x859fe39d…effa
0x34b655…2a6f
4 touches
1 conflict
0x875d9d25…f692
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd3537c0b…fb4b
0x34b655…2a6f
4 touches
1 conflict
0xf073ab26…2c15
0x34b655…2a6f
4 touches
1 conflict
0x2e75aa15…0391
0x34b655…2a6f
4 touches
1 conflict
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity