← previous blocknext block →recent activity
Analyzing
Block #84,348,367
19 transactions · 14 stateful · 2026-06-28 23:34:40 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,348,367 · 19 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
1w02w13w17w08w09w110w016w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7978e9…2869
0x34b655…2a6f
6 touches
3 conflicts
0xf5970b31…f34c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0xbfe63d66…c3e6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x42bb0ac5…6b33
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
3 conflicts on slot 0xee7978e97a…ed2869
Audit this contract →
← previous block·next block →recent activity