← previous blocknext block →recent activity
Analyzing
Block #90,458,643
11 transactions · 9 stateful · 2026-07-26 10:13:30 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,458,643 · 11 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c46e97…c1b2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc11c8adf…b948
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x949fc5d9…55f3
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 0x99c46e97a0…cac1b2
Audit this contract →
← previous block·next block →recent activity