← previous blocknext block →recent activity
Analyzing
Block #84,996,726
28 transactions · 24 stateful · 2026-07-01 23:36:31 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,996,726 · 28 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
5w06w17w08w113w014w115w217w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe727ab72…768b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x0d8fcca3…d7ca
0x34b655…2a6f
4 touches
1 conflict
0x2b222b7d…2062
0x34b655…2a6f
4 touches
1 conflict
0x318f5017…38b8
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0xe727ab723d…36768b
Audit this contract →
← previous block·next block →recent activity