← previous blocknext block →recent activity
Analyzing
Block #84,073,759
17 transactions · 14 stateful · 2026-06-27 17:05:23 UTC
Parallelism
71/100
Blocked
71%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,073,759 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w17w28w310w211w212w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32359294…7113
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1d2a8430…30bf
0xa6afd3…d132
6 touches
3 conflicts
0x3de5fb8b…400a
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xada193dc…5c7d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x3235929431…327113
Audit this contract →
← previous block·next block →recent activity