← previous blocknext block →recent activity
Analyzing
Block #85,991,308
30 transactions · 22 stateful · 2026-07-06 14:06:31 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,991,308 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w111w013w014w117w019w122w123w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebc0f21b…5a23
0xf59d81…17a3
4 touches
1 conflict
0x9da6e429…074d
0xa6afd3…d132
4 touches
1 conflict
0xd3a1c1e4…db96
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x52342825…6e5c
0x34b655…2a6f
4 touches
1 conflict
0x59645a97…3ca1
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: 0xf59d81cd…1017a3
1 conflict on slot 0xebc0f21b88…6e5a23
Audit this contract →
← previous block·next block →recent activity