← previous blocknext block →recent activity
Analyzing
Block #89,674,900
15 transactions · 14 stateful · 2026-07-23 16:07:30 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,674,900 · 15 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
2w03w14w25w36w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48a04593…db55
0x34b655…2a6f
4 touches
1 conflict
0x5edb8bbe…bc75
0x34b655…2a6f
4 touches
1 conflict
0xeab8b522…d3e6
0x34b655…2a6f
4 touches
1 conflict
0x11ebadec…5b43
0x34b655…2a6f
4 touches
1 conflict
0xd67a17a8…2cf4
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