← previous blocknext block →recent activity
Analyzing
Block #85,223,984
17 transactions · 13 stateful · 2026-07-03 00:54:11 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,223,984 · 17 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
1w03w18w010w011w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2862d04…388c
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x14928b69…b98f
0x34b655…2a6f
4 touches
1 conflict
0x4384dd01…4f99
0x34b655…2a6f
4 touches
1 conflict
0x2c8bf7d9…3cc7
0xc8689a…ee79
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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 0xd2862d04eb…53388c
Audit this contract →
← previous block·next block →recent activity