← previous blocknext block →recent activity
Analyzing
Block #90,636,415
12 transactions · 11 stateful · 2026-07-27 01:07:50 UTC
Parallelism
50/100
Blocked
45%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,636,415 · 12 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
1w02w13w24w35w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cfabf20…d256
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x3f2c4746…92f2
0x34b655…2a6f
4 touches
1 conflict
0x1fdc16cf…015e
0x34b655…2a6f
4 touches
1 conflict
0xcd6b42fb…a313
0x34b655…2a6f
4 touches
1 conflict
0xec152baf…a069
0x34b655…2a6f
4 touches
1 conflict
0xfcee9763…34fd
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 0x6cfabf2053…bad256
Audit this contract →
← previous block·next block →recent activity