← previous blocknext block →recent activity
Analyzing
Block #86,300,524
31 transactions · 26 stateful · 2026-07-08 00:30:47 UTC
Parallelism
84/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,300,524 · 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
1w02w05w16w07w112w115w116w217w319w020w123w024w125w226w327w428w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x2cec7b1d…770e
0x34b655…2a6f
4 touches
1 conflict
0x64461c10…e86d
0x34b655…2a6f
4 touches
1 conflict
0x7c83f524…c24d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity