← previous blocknext block →recent activity
Analyzing
Block #90,526,351
8 transactions · 8 stateful · 2026-07-26 15:54:09 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,526,351 · 8 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
2w03w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0x18de67b0…bf35
0x34b655…2a6f
4 touches
1 conflict
0x1da947c4…f74e
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x3823a559…aaa7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ab9d210…1d5b
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 0x0fe1e6e0ec…9df553
Audit this contract →
← previous block·next block →recent activity