← previous blocknext block →recent activity
Analyzing
Block #89,869,824
10 transactions · 9 stateful · 2026-07-24 08:31:05 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,869,824 · 10 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
1w04w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72c8aeb2…9921
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0x4b91d965…7dcb
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
2 touches
0 conflicts
0x72083f0d…082a
0x34b655…2a6f
2 touches
0 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
2 touches
0 conflicts
0xba228f10…2593
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x72c8aeb26f…899921
Audit this contract →
← previous block·next block →recent activity