← previous blocknext block →recent activity
Analyzing
Block #86,779,310
17 transactions · 12 stateful · 2026-07-10 05:52:32 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,779,310 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb9cf89…166c
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x50e10826…843b
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9af7fe70…3e49
0x40c49f…2af0
2 touches
0 conflicts
0xcd98a779…23ee
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 0xdbb9cf894a…87166c
Audit this contract →
← previous block·next block →recent activity