← previous blocknext block →recent activity
Analyzing
Block #90,535,021
11 transactions · 11 stateful · 2026-07-26 16:37:45 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,535,021 · 11 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
1w02w14w25w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6396a4c4…f626
0x34b655…2a6f
6 touches
3 conflicts
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x00bbd28c…e227
0x34b655…2a6f
4 touches
1 conflict
0x1fdc16cf…015e
0x34b655…2a6f
4 touches
1 conflict
0x26d5de2b…199e
0x34b655…2a6f
4 touches
1 conflict
0x2a5e2b11…1c2b
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
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 0x6396a4c45b…5cf626
Audit this contract →
← previous block·next block →recent activity