← previous blocknext block →recent activity
Analyzing
Block #90,635,683
8 transactions · 7 stateful · 2026-07-27 01:04:09 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,635,683 · 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74c7e4b2…d9d3
0x34b655…2a6f
6 touches
3 conflicts
0x3e30f1bf…6453
0x34b655…2a6f
4 touches
1 conflict
0x63e5511c…d6a7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfafedcbd…17d4
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
0x34b655…2a6f
2 touches
0 conflicts
0x49c1a7b0…d270
0x34b655…2a6f
2 touches
0 conflicts
0x52f052e8…60a7
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 0x74c7e4b28f…dbd9d3
Audit this contract →
← previous block·next block →recent activity