← previous blocknext block →recent activity
Analyzing
Block #90,792,123
15 transactions · 14 stateful · 2026-07-27 14:11:09 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,792,123 · 15 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
3w04w15w06w17w28w39w410w512w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xe2978062…2000
0x34b655…2a6f
4 touches
1 conflict
0x3e8569e7…04d7
0x34b655…2a6f
4 touches
1 conflict
0x62dbeb4d…a388
0x34b655…2a6f
4 touches
1 conflict
0xed3dd803…4cbb
0xd32edf…ff58
3 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x334aa47d…cac0
0x34b655…2a6f
2 touches
0 conflicts
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity