← previous blocknext block →recent activity
Analyzing
Block #90,028,343
14 transactions · 13 stateful · 2026-07-24 21:49:03 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,028,343 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w28w110w311w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21cb35dd…1f66
0x34b655…2a6f
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0x8eef368f…aa21
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xb9f0b0dc…4827
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0xf9e23360…8ef7
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 0x21cb35dd46…db1f66
Audit this contract →
← previous block·next block →recent activity