← previous blocknext block →recent activity
Analyzing
Block #84,514,237
44 transactions · 33 stateful · 2026-06-29 18:00:42 UTC
Parallelism
86/100
Blocked
61%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,514,237 · 44 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w09w210w011w112w215w016w117w218w022w123w324w425w426w536w137w240w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
8 touches
6 conflicts
0x49b0842d…0a93
0x34b655…2a6f
6 touches
3 conflicts
0x6e2becf4…0c5f
0x34b655…2a6f
6 touches
3 conflicts
0x94710b77…a921
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
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: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity