← previous blocknext block →recent activity
Analyzing
Block #84,279,197
33 transactions · 30 stateful · 2026-06-28 15:53:49 UTC
Parallelism
61/100
Blocked
70%
Avg conflicts / tx
2.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #84,279,197 · 33 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w28w39w410w511w612w713w814w915w1016w1117w1224w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
26 touches
78 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x43a7d995…a48f
0x065c9d…c394
6 touches
3 conflicts
0x2a513dfb…2bb8
0x34b655…2a6f
6 touches
3 conflicts
0x32409e80…a396
0x34b655…2a6f
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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: 0xd637b38f…c64160
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity