← previous blocknext block →recent activity
Analyzing
Block #89,701,773
16 transactions · 15 stateful · 2026-07-23 18:23:11 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,701,773 · 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
7w09w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb757e0c5…7a89
0x34b655…2a6f
4 touches
1 conflict
0xbe581d31…e0b9
0x34b655…2a6f
4 touches
1 conflict
0xc3656cd1…8269
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x16b2c220…a431
0x34b655…2a6f
4 touches
1 conflict
0x487402a1…90b7
0x34b655…2a6f
4 touches
1 conflict
0x487402a1…90b8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
1 conflict on slot 0xb757e0c54f…b57a89
Audit this contract →
← previous block·next block →recent activity