← previous blocknext block →recent activity
Analyzing
Block #90,040,593
7 transactions · 6 stateful · 2026-07-24 22:50:47 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,040,593 · 7 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53fcfcd4…5c82
0x34b655…2a6f
4 touches
1 conflict
0x04535e24…7c8c
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x53fcfcd4…5c81
0x34b655…2a6f
4 touches
1 conflict
0x7241e2d3…8529
0x34b655…2a6f
4 touches
1 conflict
0xb0a58df7…87e3
0x34b655…2a6f
4 touches
1 conflict
0x24b56d25…9f26
0x34b655…2a6f
2 touches
0 conflicts
0x35fe7fc3…8e54
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 0x53fcfcd408…8e5c82
Audit this contract →
← previous block·next block →recent activity