← previous blocknext block →recent activity
Analyzing
Block #90,893,223
6 transactions · 6 stateful · 2026-07-27 22:39:52 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,893,223 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72c8aeb2…9921
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf7759f1d…0ad4
0x34b655…2a6f
4 touches
1 conflict
0x0387c9ac…b3c5
0x34b655…2a6f
2 touches
0 conflicts
0x0644aa4a…636f
0x34b655…2a6f
2 touches
0 conflicts
0x0ebd84aa…d159
0x34b655…2a6f
2 touches
0 conflicts
0x183c10a3…2e0a
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 0x72c8aeb26f…899921
Audit this contract →
← previous block·next block →recent activity