← previous blocknext block →recent activity
Analyzing
Block #86,103,974
20 transactions · 17 stateful · 2026-07-07 02:38:32 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,103,974 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w08w110w011w113w115w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0xa19aba84…8922
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1674b7f1…ae37
0xa6afd3…d132
4 touches
1 conflict
0x46b62326…9b3c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xa04c12fe…40c1
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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 0xe5eb3c3335…0c0e3a
Audit this contract →
← previous block·next block →recent activity