← previous blocknext block →recent activity
Analyzing
Block #86,448,776
17 transactions · 17 stateful · 2026-07-08 17:01:15 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,448,776 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fd328f3…701f
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x080ec687…da80
0x34b655…2a6f
4 touches
1 conflict
0x330a0e84…0d91
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
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 0x6fd328f36d…0d701f
Audit this contract →
← previous block·next block →recent activity