← previous blocknext block →recent activity
Analyzing
Block #90,623,920
16 transactions · 14 stateful · 2026-07-27 00:04:57 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,623,920 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w410w011w112w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x64dfceb0…c5d7
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x4d094aeb…b8b1
0x34b655…2a6f
4 touches
1 conflict
0x539c67d9…5e65
0x34b655…2a6f
4 touches
1 conflict
0x6e0e8837…2e59
0x34b655…2a6f
4 touches
1 conflict
0x74c7e4b2…d9d3
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity