← previous blocknext block →recent activity
Analyzing
Block #85,108,243
12 transactions · 12 stateful · 2026-07-02 12:02:37 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,108,243 · 12 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
2w04w06w17w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30fa662a…06e0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe0532746…0224
0x851145…3f07
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0xa05b1444…e3c0
0x34b655…2a6f
4 touches
1 conflict
0xb980888b…6d4d
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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
3 conflicts on slot 0x30fa662a9f…0906e0
Audit this contract →
← previous block·next block →recent activity