← previous blocknext block →recent activity
Analyzing
Block #89,735,343
14 transactions · 12 stateful · 2026-07-23 21:12:37 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,735,343 · 14 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
2w03w17w210w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xefa57583…ca11
0x34b655…2a6f
4 touches
1 conflict
0x8a72512c…4624
0x34b655…2a6f
4 touches
1 conflict
0xb700a36d…478c
0x34b655…2a6f
4 touches
1 conflict
0xb725b113…4cf6
0x34b655…2a6f
4 touches
1 conflict
0xb9d105ec…ea70
0x34b655…2a6f
4 touches
1 conflict
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0xcd899d87…c031
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity