← previous blocknext block →recent activity
Analyzing
Block #86,741,744
12 transactions · 11 stateful · 2026-07-10 01:41:38 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,741,744 · 12 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
1w02w14w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae9b213d…a4f7
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0x230a3fb0…e64c
0x34b655…2a6f
4 touches
1 conflict
0x3b527e8b…2cf6
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0x4442e33b…3951
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 0xae9b213d9a…71a4f7
Audit this contract →
← previous block·next block →recent activity