← previous blocknext block →recent activity
Analyzing
Block #90,644,826
8 transactions · 7 stateful · 2026-07-27 01:50:08 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,644,826 · 8 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
2w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24eaf46d…8c2e
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x013a6b08…d120
0x34b655…2a6f
2 touches
0 conflicts
0x04142bcf…67cb
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf6
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x06c980ab…5577
0x34b655…2a6f
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
3 conflicts on slot 0x24eaf46d19…768c2e
Audit this contract →
← previous block·next block →recent activity