← previous blocknext block →recent activity
Analyzing
Block #84,355,960
20 transactions · 18 stateful · 2026-06-29 00:25:21 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,355,960 · 20 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
1w02w15w06w18w09w111w012w213w116w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708619a6…d52a
0x34b655…2a6f
8 touches
6 conflicts
0x8af11205…8cf2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1222e42d…7dc8
0x34b655…2a6f
4 touches
1 conflict
0x50260e8c…4789
0x34b655…2a6f
4 touches
1 conflict
0x76685fb7…034a
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
6 conflicts on slot 0x708619a655…90d52a
Audit this contract →
← previous block·next block →recent activity