← previous blocknext block →recent activity
Analyzing
Block #86,308,023
30 transactions · 18 stateful · 2026-07-08 01:20:56 UTC
Parallelism
87/100
Blocked
56%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,308,023 · 30 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
1w02w03w16w17w213w014w118w219w020w321w123w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x46b62326…9b3c
0xa6afd3…d132
6 touches
3 conflicts
0x89750670…2dea
0xa6afd3…d132
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
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 0xe8eae8a323…64bacc
Audit this contract →
← previous block·next block →recent activity