← previous blocknext block →recent activity
Analyzing
Block #84,279,196
37 transactions · 35 stateful · 2026-06-28 15:53:49 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
1.49
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,279,196 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w37w423w324w425w127w428w329w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
8 touches
6 conflicts
0xbc9aaf19…8cfd
0x34b655…2a6f
8 touches
6 conflicts
0xe1e58d05…117f
0x34b655…2a6f
8 touches
6 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: Perpl
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity