← previous blocknext block →recent activity
Analyzing
Block #90,037,048
10 transactions · 9 stateful · 2026-07-24 22:32:52 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,037,048 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31ec17e3…8912
0x34b655…2a6f
4 touches
1 conflict
0x330df1e6…7587
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x1cda40c9…d853
0x34b655…2a6f
2 touches
0 conflicts
0x1d446775…5212
0x34b655…2a6f
2 touches
0 conflicts
0x27778a53…f135
0x34b655…2a6f
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 0x31ec17e351…8e8912
Audit this contract →
← previous block·next block →recent activity