← previous blocknext block →recent activity
Analyzing
Block #90,867,571
14 transactions · 14 stateful · 2026-07-27 20:30:51 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,867,571 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w310w411w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fafc50a…e3b0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0x77cf3c7b…a722
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 0x7fafc50aa9…69e3b0
Audit this contract →
← previous block·next block →recent activity