← previous blocknext block →recent activity
Analyzing
Block #85,219,054
14 transactions · 12 stateful · 2026-07-03 00:21:22 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,219,054 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x022b49db…a477
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2c5cd08e…a280
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x25e3730b…24a9
0x34b655…2a6f
2 touches
0 conflicts
0x39776415…dfb4
0x34b655…2a6f
2 touches
0 conflicts
0x4bdb0ed2…89fe
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
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 0x022b49dbc5…d3a477
Audit this contract →
← previous block·next block →recent activity