← previous blocknext block →recent activity
Analyzing
Block #89,749,274
16 transactions · 13 stateful · 2026-07-23 22:23:03 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,749,274 · 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
1w02w16w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0xd15528dd…6cb3
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0009
0x04ddf6…7f33
2 touches
0 conflicts
0xaeabffea…5dd4
0x0a3323…0a3c
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: 0x0a332311…6e0a3c
1 conflict on slot 0x0ef74796d8…7ccd18
Audit this contract →
← previous block·next block →recent activity