← previous blocknext block →recent activity
Analyzing
Block #90,813,912
14 transactions · 13 stateful · 2026-07-27 16:00:52 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,813,912 · 14 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
3w06w17w28w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5cc7e5aa…8945
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x77a700dc…2f59
0x34b655…2a6f
4 touches
1 conflict
0x99bc8b1a…2c66
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 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity