← previous blocknext block →recent activity
Analyzing
Block #90,236,857
15 transactions · 14 stateful · 2026-07-25 15:22:57 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,236,857 · 15 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
1w04w06w09w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x722f5f69…a1eb
0x065c9d…c394
4 touches
1 conflict
0x794a88aa…32bb
0x065c9d…c394
3 touches
1 conflict
0xf2ba025e…e594
0x065c9d…c394
3 touches
1 conflict
0xf2ba025e…e595
0x065c9d…c394
3 touches
1 conflict
0x00000000…0002
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0004
0x453805…c7fd
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 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity