← previous blocknext block →recent activity
Analyzing
Block #90,235,477
18 transactions · 17 stateful · 2026-07-25 15:16:00 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,235,477 · 18 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
1w02w13w05w06w19w210w211w112w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fe45a2e…f687
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
6 touches
3 conflicts
0x7e162301…9c1b
0x34b655…2a6f
6 touches
3 conflicts
0xf50ebbf7…73c8
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xdc50598b…8536
0x065c9d…c394
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 0x3fe45a2e89…a9f687
Audit this contract →
← previous block·next block →recent activity