← previous blocknext block →recent activity
Analyzing
Block #86,758,853
14 transactions · 12 stateful · 2026-07-10 03:35:56 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,758,853 · 14 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
1w02w13w05w16w27w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6a8d7ce…d4f1
0x34b655…2a6f
8 touches
6 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0xf4a27876…b09c
0x34b655…2a6f
4 touches
1 conflict
0xe3e5befe…fcdb
0x34b655…2a6f
4 touches
1 conflict
0xe3e5befe…fcda
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f787
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f788
0x34b655…2a6f
4 touches
1 conflict
0x19272363…38bc
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
6 conflicts on slot 0xa6a8d7cec5…24d4f1
Audit this contract →
← previous block·next block →recent activity