← previous blocknext block →recent activity
Analyzing
Block #90,531,152
10 transactions · 10 stateful · 2026-07-26 16:18:17 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,531,152 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x44df3c2a…bafe
0x34b655…2a6f
4 touches
1 conflict
0x44df3c2a…baff
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x7a2c83a3…a29a
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 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity