← previous blocknext block →recent activity
Analyzing
Block #85,195,326
19 transactions · 14 stateful · 2026-07-02 21:43:21 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,195,326 · 19 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
1w03w04w17w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x55447ef3…7817
0x34b655…2a6f
4 touches
1 conflict
0x6ca10f59…c0d3
0x34b655…2a6f
4 touches
1 conflict
0x7239a7a0…e541
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
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
1 conflict on slot 0x06aed19eee…1cca57
Audit this contract →
← previous block·next block →recent activity