← previous blocknext block →recent activity
Analyzing
Block #84,017,822
13 transactions · 11 stateful · 2026-06-27 10:52:51 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,017,822 · 13 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
6w07w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x42341814…60f1
0x34b655…2a6f
4 touches
1 conflict
0x1741893b…c889
0x34b655…2a6f
2 touches
0 conflicts
0x200db05e…6327
0x34b655…2a6f
2 touches
0 conflicts
0x48a2b821…513e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x74fd0a9bd1…ea3aaa
Audit this contract →
← previous block·next block →recent activity