← previous blocknext block →recent activity
Analyzing
Block #90,948,674
12 transactions · 12 stateful · 2026-07-28 03:18:49 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,948,674 · 12 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
1w02w13w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b9b421…f42c
0x34b655…2a6f
6 touches
3 conflicts
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0x327c57dd…836d
0x34b655…2a6f
4 touches
1 conflict
0xb839a1e8…22b3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc1a6feba…8440
0x34b655…2a6f
4 touches
1 conflict
0xc4ce67e5…672c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x33b9b4211a…c0f42c
Audit this contract →
← previous block·next block →recent activity