← previous blocknext block →recent activity
Analyzing
Block #89,700,870
14 transactions · 12 stateful · 2026-07-23 18:18:38 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,700,870 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5deef6f…6c3f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x103aaa01…bdc1
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 0xa5deef6f49…976c3f
Audit this contract →
← previous block·next block →recent activity