← previous blocknext block →recent activity
Analyzing
Block #86,327,931
17 transactions · 14 stateful · 2026-07-08 03:33:57 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,327,931 · 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
5w010w011w112w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32810c72…e6c0
0x34b655…2a6f
4 touches
1 conflict
0x7b55198a…b946
0x34b655…2a6f
4 touches
1 conflict
0x830b63a6…8105
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xea434044…5fd7
0x34b655…2a6f
4 touches
1 conflict
0xad63663f…2db4
0x40c49f…2af0
2 touches
0 conflicts
0xd150aeb2…3f63
0x40c49f…2af0
2 touches
0 conflicts
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 0x32810c72da…16e6c0
Audit this contract →
← previous block·next block →recent activity