← previous blocknext block →recent activity
Analyzing
Block #84,538,002
26 transactions · 21 stateful · 2026-06-29 20:39:05 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,538,002 · 26 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
1w03w011w014w015w116w117w219w220w323w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x77dc4958…659e
0x34b655…2a6f
6 touches
3 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity