← previous blocknext block →recent activity
Analyzing
Block #86,747,074
13 transactions · 7 stateful · 2026-07-10 02:17:16 UTC
Parallelism
77/100
Blocked
29%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,747,074 · 13 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
4w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x53355553…2976
0x34b655…2a6f
4 touches
1 conflict
0xab774675…75f7
0x34b655…2a6f
4 touches
1 conflict
0xb7b1a9a4…0c7e
0x34b655…2a6f
4 touches
1 conflict
0xb7b1a9a4…0c7f
0x34b655…2a6f
4 touches
1 conflict
0xd69bec2a…118e
0x34b655…2a6f
4 touches
1 conflict
0x58ce2a34…8e41
0x34b655…2a6f
4 touches
1 conflict
0x5b8a1a43…4aea
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity