← previous blocknext block →recent activity
Analyzing
Block #90,960,089
10 transactions · 10 stateful · 2026-07-28 04:16:13 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,960,089 · 10 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
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x334aa47d…cac0
0x34b655…2a6f
2 touches
0 conflicts
0x4b2d9b6d…c213
0x34b655…2a6f
2 touches
0 conflicts
0x5177b5c6…b946
0x34b655…2a6f
2 touches
0 conflicts
0x64d76184…af55
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 0x3cb7ee74c7…7db8a5
Audit this contract →
← previous block·next block →recent activity