← previous blocknext block →recent activity
Analyzing
Block #90,289,089
13 transactions · 10 stateful · 2026-07-25 19:46:50 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,289,089 · 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
4w06w18w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90670859…26c7
0x34b655…2a6f
4 touches
1 conflict
0xe3471350…0bcf
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x58aa2cb3…5758
0x34b655…2a6f
2 touches
0 conflicts
0x5d77346a…863a
0x34b655…2a6f
2 touches
0 conflicts
0x7d5a6f66…aba7
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 0x9067085931…fb26c7
Audit this contract →
← previous block·next block →recent activity