← previous blocknext block →recent activity
Analyzing
Block #89,847,737
10 transactions · 10 stateful · 2026-07-24 06:39:59 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,847,737 · 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
2w05w16w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb027a20d…5efe
0x34b655…2a6f
4 touches
1 conflict
0xbc586c28…a4f5
0x34b655…2a6f
4 touches
1 conflict
0xbef1e8f5…ae70
0x34b655…2a6f
4 touches
1 conflict
0xaffb690e…61d0
0x34b655…2a6f
4 touches
1 conflict
0xaffb690e…61d1
0x34b655…2a6f
4 touches
1 conflict
0x59164e7a…7e0a
0x34b655…2a6f
4 touches
1 conflict
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0xb027a20d80…265efe
Audit this contract →
← previous block·next block →recent activity