← previous blocknext block →recent activity
Analyzing
Block #85,674,017
13 transactions · 13 stateful · 2026-07-05 02:51:05 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,674,017 · 13 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
1w02w16w07w18w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cdad76f…2bed
0x34b655…2a6f
4 touches
1 conflict
0x56f59993…2c32
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5087444f…5acf
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
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
1 conflict on slot 0x6cdad76fd1…3a2bed
Audit this contract →
← previous block·next block →recent activity