← previous blocknext block →recent activity
Analyzing
Block #89,543,729
18 transactions · 15 stateful · 2026-07-23 02:00:16 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,543,729 · 18 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
1w04w05w16w19w010w113w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xf0df1716…ba9e
0x34b655…2a6f
4 touches
1 conflict
0xf2b035ef…4746
0x34b655…2a6f
4 touches
1 conflict
0xf91eb7fa…6e70
0x34b655…2a6f
4 touches
1 conflict
0x0bb0061e…dfbc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x410376a5…b133
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