← previous blocknext block →recent activity
Analyzing
Block #90,680,344
8 transactions · 6 stateful · 2026-07-27 04:48:50 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,680,344 · 8 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x5110a94f…86d2
0x34b655…2a6f
4 touches
1 conflict
0x0ae356af…7a5e
0x34b655…2a6f
4 touches
1 conflict
0x379dc435…6616
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
0x34b655…2a6f
2 touches
0 conflicts
0xb505850e…8039
0x34b655…2a6f
2 touches
0 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
2 touches
0 conflicts
0xb9694185…1504
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 0x5110a94ff5…1e86d1
Audit this contract →
← previous block·next block →recent activity