← previous blocknext block →recent activity
Analyzing
Block #90,068,819
23 transactions · 20 stateful · 2026-07-25 01:13:36 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,068,819 · 23 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
2w03w16w07w18w29w312w213w416w217w318w220w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5031114…58ac
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xcd9abe80…5031
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1dd28681…d842
0x34b655…2a6f
6 touches
3 conflicts
0x6c7d4ae1…7bd3
0x34b655…2a6f
6 touches
3 conflicts
0x8861b270…e0cb
0x34b655…2a6f
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 0xc503111436…e358ac
Audit this contract →
← previous block·next block →recent activity