← previous blocknext block →recent activity
Analyzing
Block #86,243,824
21 transactions · 21 stateful · 2026-07-07 18:12:20 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,243,824 · 21 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
1w02w16w07w18w210w213w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x59dbc306…f976
0x34b655…2a6f
4 touches
1 conflict
0x62c3109e…aa25
0x34b655…2a6f
4 touches
1 conflict
0xcc25f1e5…2cac
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
3 conflicts on slot 0xd800e635bc…14b1d7
Audit this contract →
← previous block·next block →recent activity