← previous blocknext block →recent activity
Analyzing
Block #86,923,644
19 transactions · 16 stateful · 2026-07-10 21:57:27 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,923,644 · 19 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
2w03w14w26w010w116w217w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x0cf9e21c…9f5a
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x3c610031…a65e
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x8ed2e166…994b
0x34b655…2a6f
4 touches
1 conflict
0x9e9ffe69…e039
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 0x94ba9c4a07…0c41d8
Audit this contract →
← previous block·next block →recent activity