← previous blocknext block →recent activity
Analyzing
Block #85,927,214
21 transactions · 16 stateful · 2026-07-06 06:58:38 UTC
Parallelism
90/100
Blocked
6%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,927,214 · 21 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
16w018w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x489fafcb…9780
0x065c9d…c394
2 touches
0 conflicts
0x894f4c1c…3a31
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
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 0x9ae859dbf8…e82d84
Audit this contract →
← previous block·next block →recent activity