← previous blocknext block →recent activity
Analyzing
Block #86,443,912
16 transactions · 13 stateful · 2026-07-08 16:28:42 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,443,912 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w08w19w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x211d520a…bf67
0x34b655…2a6f
4 touches
1 conflict
0x2b5cb9f0…1d10
0x34b655…2a6f
4 touches
1 conflict
0x3c770221…6ef4
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c7a4dca…ad0c
0x34b655…2a6f
4 touches
1 conflict
0x4ec8d1b4…4e6e
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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
1 conflict on slot 0x211d520ae5…c9bf67
Audit this contract →
← previous block·next block →recent activity