← previous blocknext block →recent activity
Analyzing
Block #89,699,947
16 transactions · 16 stateful · 2026-07-23 18:14:00 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,699,947 · 16 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
1w02w03w17w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x9a18a78f…6f7e
0x065c9d…c394
3 touches
1 conflict
0x4dbc0a48…e0d7
0x065c9d…c394
2 touches
0 conflicts
0xf432f1a8…fe09
0x065c9d…c394
2 touches
0 conflicts
0xf99a4dd0…8f14
0x065c9d…c394
2 touches
0 conflicts
0xfe90d032…14ed
0x065c9d…c394
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity