← previous blocknext block →recent activity
Analyzing
Block #90,894,172
13 transactions · 11 stateful · 2026-07-27 22:44:39 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,894,172 · 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
4w05w16w17w28w39w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x18a3a88d…3c12
0x34b655…2a6f
4 touches
1 conflict
0x18dc3f96…0d05
0x34b655…2a6f
4 touches
1 conflict
0x676baad1…1c45
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity