← previous blocknext block →recent activity
Analyzing
Block #90,515,324
15 transactions · 15 stateful · 2026-07-26 14:58:41 UTC
Parallelism
87/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,515,324 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ee667a1…2a60
0x34b655…2a6f
4 touches
1 conflict
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0xd68cd74f…9826
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x32181e64…29ee
0x34b655…2a6f
2 touches
0 conflicts
0x3d7c5570…31b1
0x34b655…2a6f
2 touches
0 conflicts
0x487aa334…7ef2
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
1 conflict on slot 0x5ee667a109…d62a60
Audit this contract →
← previous block·next block →recent activity