← previous blocknext block →recent activity
Analyzing
Block #85,824,811
19 transactions · 19 stateful · 2026-07-05 19:36:29 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,824,811 · 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
4w05w17w08w110w012w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7ea53c99…0c3e
0x34b655…2a6f
4 touches
1 conflict
0x828cefbb…7934
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa19aba84…8922
0xa6afd3…d132
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 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity