← previous blocknext block →recent activity
Analyzing
Block #90,374,473
10 transactions · 10 stateful · 2026-07-26 03:02:35 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,374,473 · 10 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
1w02w13w26w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2b37cdc…e470
0x34b655…2a6f
6 touches
3 conflicts
0x6dca49f6…b5a7
0x34b655…2a6f
6 touches
3 conflicts
0xb7fb66e8…4f94
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9775559a…a8ec
0x34b655…2a6f
6 touches
3 conflicts
0x72bf3cf6…f43b
0x34b655…2a6f
5 touches
3 conflicts
0xaf8ce2ab…51b9
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
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 0xc2b37cdc32…c4e470
Audit this contract →
← previous block·next block →recent activity