← previous blocknext block →recent activity
Analyzing
Block #90,312,984
12 transactions · 12 stateful · 2026-07-25 21:48:18 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,312,984 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dcea2f…25e6
0x34b655…2a6f
6 touches
3 conflicts
0xd1f9c118…1d02
0x34b655…2a6f
4 touches
1 conflict
0x26e32e90…8827
0x34b655…2a6f
4 touches
1 conflict
0x3e3efa40…fb7f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x66649bfc…6f75
0x34b655…2a6f
4 touches
1 conflict
0x7d5a6f66…aba7
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
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 0x16dcea2fe5…b525e6
Audit this contract →
← previous block·next block →recent activity