← previous blocknext block →recent activity
Analyzing
Block #84,460,317
20 transactions · 19 stateful · 2026-06-29 12:00:53 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,460,317 · 20 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
3w07w08w09w010w112w114w115w216w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xfd7dc5f1…38cc
0x34b655…2a6f
6 touches
3 conflicts
0x601978e3…1979
0x34b655…2a6f
4 touches
1 conflict
0x6e9c6f6d…7ea7
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity