← previous blocknext block →recent activity
Analyzing
Block #90,683,213
13 transactions · 10 stateful · 2026-07-27 05:03:15 UTC
Parallelism
62/100
Blocked
60%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,683,213 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w39w411w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7b1189e…d092
0x34b655…2a6f
6 touches
3 conflicts
0x5a100ac0…96d3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0c376bba…95b1
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
3 conflicts on slot 0xc7b1189e8a…30d092
Audit this contract →
← previous block·next block →recent activity