← previous blocknext block →recent activity
Analyzing
Block #90,823,448
13 transactions · 12 stateful · 2026-07-27 16:48:50 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,823,448 · 13 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
1w02w13w04w17w28w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02ad5c19…f593
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xda65cebb…3038
0x34b655…2a6f
4 touches
1 conflict
0xfc0e8d5c…cfe6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00cd9338…40d2
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
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 0x02ad5c1905…1df593
Audit this contract →
← previous block·next block →recent activity