← previous blocknext block →recent activity
Analyzing
Block #90,914,955
23 transactions · 19 stateful · 2026-07-28 00:29:13 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,914,955 · 23 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
1w03w04w05w16w27w38w29w311w112w113w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x08dfb75b…c83c
0x34b655…2a6f
4 touches
1 conflict
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x44f26cbe…58c2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c3a08af…03e1
0x34b655…2a6f
4 touches
1 conflict
0x646278ac…2ebf
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity