← previous blocknext block →recent activity
Analyzing
Block #86,483,467
17 transactions · 14 stateful · 2026-07-08 20:53:25 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,483,467 · 17 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
1w02w15w06w17w08w110w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6827c800…a1a1
0x34b655…2a6f
4 touches
1 conflict
0x71708ff5…aac8
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xbf78ee7f…e7fd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0dd44476…ef40
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 0x6827c80013…e0a1a1
Audit this contract →
← previous block·next block →recent activity