← previous blocknext block →recent activity
Analyzing
Block #90,023,966
14 transactions · 13 stateful · 2026-07-24 21:27:00 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,023,966 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w110w011w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xecf37346…0b1b
0x34b655…2a6f
4 touches
1 conflict
0x6d48c480…7ddf
0xd32edf…ff58
3 touches
1 conflict
0x046c0d57…f055
0x065c9d…c394
2 touches
0 conflicts
0x0d7807bf…9fda
0x065c9d…c394
2 touches
0 conflicts
0x3246eb65…c06e
0x065c9d…c394
2 touches
0 conflicts
0x3d088c98…bef0
0x065c9d…c394
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
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity