← previous blocknext block →recent activity
Analyzing
Block #89,413,010
19 transactions · 17 stateful · 2026-07-22 11:27:00 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,413,010 · 19 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
2w03w06w17w28w09w110w316w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33f54bd6…9ac3
0x34b655…2a6f
6 touches
3 conflicts
0x93d4b4e9…5daa
0x851145…3f07
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe33a222b…710f
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x155e52ca…fac7
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
3 conflicts on slot 0x33f54bd6fe…149ac3
Audit this contract →
← previous block·next block →recent activity