← previous blocknext block →recent activity
Analyzing
Block #90,223,231
13 transactions · 12 stateful · 2026-07-25 14:14:16 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,223,231 · 13 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
1w05w07w18w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x5110a94f…86d2
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x026b0afe…f71d
0x34b655…2a6f
4 touches
1 conflict
0x519e0fef…7303
0x34b655…2a6f
2 touches
0 conflicts
0x58bce2bb…a259
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0x5110a94ff5…1e86d1
Audit this contract →
← previous block·next block →recent activity