← previous blocknext block →recent activity
Analyzing
Block #84,495,336
13 transactions · 11 stateful · 2026-06-29 15:54:34 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,495,336 · 13 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
1w02w14w05w16w07w28w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x083984dd…0acb
0x40c49f…2af0
4 touches
1 conflict
0x5e51dc74…db2a
0x40c49f…2af0
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9282c7d…254f
0x065c9d…c394
4 touches
1 conflict
0xe75cebb6…6b36
0x065c9d…c394
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: 0x40c49f17…d22af0
1 conflict on slot 0xdfc5f34630…0b7b42
Audit this contract →
← previous block·next block →recent activity