← previous blocknext block →recent activity
Analyzing
Block #90,853,823
8 transactions · 7 stateful · 2026-07-27 19:21:37 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,853,823 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd26745e2…81cb
0x34b655…2a6f
4 touches
1 conflict
0x08c8d9b3…e032
0x065c9d…c394
2 touches
0 conflicts
0x1c04a22d…d43b
0x065c9d…c394
2 touches
0 conflicts
0x21b02552…c1c7
0x065c9d…c394
2 touches
0 conflicts
0x2a0382ea…bff7
0x065c9d…c394
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 0x3b56f79b81…31310f
Audit this contract →
← previous block·next block →recent activity