← previous blocknext block →recent activity
Analyzing
Block #90,453,966
9 transactions · 9 stateful · 2026-07-26 09:49:59 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,453,966 · 9 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
4w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2ffa1f3…d3ae
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0x1cc2362d…1fb1
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
2 touches
0 conflicts
0x3fc48818…2eda
0x34b655…2a6f
2 touches
0 conflicts
0x4515e9d4…e548
0x34b655…2a6f
2 touches
0 conflicts
0x6713b018…05f3
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 0xd2ffa1f3c7…48d3ae
Audit this contract →
← previous block·next block →recent activity