← previous blocknext block →recent activity
Analyzing
Block #89,769,809
21 transactions · 19 stateful · 2026-07-24 00:06:44 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,769,809 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w28w312w114w218w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x4aa7bc6e…96f3
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x74514b47…86eb
0x34b655…2a6f
4 touches
1 conflict
0xd6d06e7d…1f4b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity