← previous blocknext block →recent activity
Analyzing
Block #86,300,002
31 transactions · 27 stateful · 2026-07-08 00:27:19 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,300,002 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w09w110w211w213w115w216w317w418w219w320w021w326w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0xfadb0e19…7a27
0x851145…3f07
6 touches
3 conflicts
0x7d6cbd65…0e0a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xda8d6085…7b09
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 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
6 conflicts on slot 0xbe9baf16a9…e6df37
Audit this contract →
← previous block·next block →recent activity