← previous blocknext block →recent activity
Analyzing
Block #90,623,602
16 transactions · 14 stateful · 2026-07-27 00:03:21 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,623,602 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w06w17w210w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce0d3554…d1dd
0x34b655…2a6f
8 touches
6 conflicts
0xad862891…5d02
0x34b655…2a6f
6 touches
3 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0xaa9f27b0…9cf2
0x34b655…2a6f
6 touches
3 conflicts
0x4ca2a6c3…ab80
0x34b655…2a6f
4 touches
1 conflict
0x5a100ac0…96d3
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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
6 conflicts on slot 0xce0d3554c7…f2d1dd
Audit this contract →
← previous block·next block →recent activity