← previous blocknext block →recent activity
Analyzing
Block #90,800,534
23 transactions · 20 stateful · 2026-07-27 14:53:29 UTC
Parallelism
74/100
Blocked
25%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,800,534 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w217w019w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d5a6f66…aba7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x16dcea2f…25e6
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x65277043…614e
0x34b655…2a6f
4 touches
1 conflict
0x81a169fb…d227
0x34b655…2a6f
4 touches
1 conflict
0x85fd15d1…e0a2
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 0x7d5a6f66a7…5eaba7
Audit this contract →
← previous block·next block →recent activity