← previous blocknext block →recent activity
Analyzing
Block #89,857,004
8 transactions · 7 stateful · 2026-07-24 07:26:35 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,857,004 · 8 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
2w03w14w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdab87f9b…3a80
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc13e1d5c…62c6
0x34b655…2a6f
4 touches
1 conflict
0xc73549e8…2001
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0xdab87f9bcc…0c3a80
Audit this contract →
← previous block·next block →recent activity