← previous blocknext block →recent activity
Analyzing
Block #86,316,152
19 transactions · 18 stateful · 2026-07-08 02:15:16 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,316,152 · 19 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
2w03w14w26w010w011w012w113w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a4133e…6110
0x34b655…2a6f
6 touches
3 conflicts
0x79d50d4a…951d
0x34b655…2a6f
6 touches
3 conflicts
0x924bac95…3f39
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
0x34b655…2a6f
4 touches
1 conflict
0xa9cc6bae…4fdb
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 0xc0a4133ed0…a76110
Audit this contract →
← previous block·next block →recent activity