← previous blocknext block →recent activity
Analyzing
Block #90,298,535
13 transactions · 11 stateful · 2026-07-25 20:34:52 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,298,535 · 13 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dd6c96e…44a7
0x34b655…2a6f
4 touches
1 conflict
0x50d44a56…fe50
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x16dcea2f…25e6
0x34b655…2a6f
4 touches
1 conflict
0x0e21a259…d2ec
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0164
0x34b655…2a6f
2 touches
0 conflicts
0x221535fb…538e
0x34b655…2a6f
2 touches
0 conflicts
0x304a552a…8fc7
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 0x6dd6c96e21…4c44a7
Audit this contract →
← previous block·next block →recent activity