← previous blocknext block →recent activity
Analyzing
Block #86,486,712
23 transactions · 18 stateful · 2026-07-08 21:15:04 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,486,712 · 23 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
1w02w14w26w09w010w111w212w013w116w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x8a751d7a…247c
0xa6afd3…d132
6 touches
3 conflicts
0x3e644b16…807b
0x34b655…2a6f
4 touches
1 conflict
0x4aa2bfeb…ca33
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity