← previous blocknext block →recent activity
Analyzing
Block #90,698,678
17 transactions · 17 stateful · 2026-07-27 06:21:03 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,698,678 · 17 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
2w03w14w26w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x67d846dd…358c
0x609679…7777
6 touches
3 conflicts
0x02059d37…b643
0x9f3832…4ae4
6 touches
3 conflicts
0x02059d37…b644
0x9f3832…4ae4
6 touches
3 conflicts
0x6faf6baf…150d
0x9f3832…4ae4
6 touches
3 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
6 touches
3 conflicts
0x8552457e…2abe
0xe1c8b7…3022
6 touches
3 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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity