← previous blocknext block →recent activity
Analyzing
Block #86,134,644
10 transactions · 10 stateful · 2026-07-07 06:03:21 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,134,644 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x04b52208…fdd6
0x34b655…2a6f
2 touches
0 conflicts
0x0c366266…77e1
0x34b655…2a6f
2 touches
0 conflicts
0x0d2fb55e…b850
0x34b655…2a6f
2 touches
0 conflicts
0x5049717f…a2f6
0x34b655…2a6f
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 0x3a6290da4d…93e683
Audit this contract →
← previous block·next block →recent activity