← previous blocknext block →recent activity
Analyzing
Block #84,996,761
19 transactions · 17 stateful · 2026-07-01 23:36:45 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
1.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,996,761 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w014w015w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x23215391…f88e
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x85b992ec…db0e
0x34b655…2a6f
8 touches
6 conflicts
0xd6418d68…bdc5
0x34b655…2a6f
8 touches
6 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
8 touches
6 conflicts
0xe727ab72…768b
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity