← previous blocknext block →recent activity
Analyzing
Block #84,353,013
32 transactions · 23 stateful · 2026-06-29 00:05:42 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,353,013 · 32 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
2w03w15w06w111w214w015w116w217w318w421w025w127w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x7534f53d…6ed4
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x753da1ce…6bbd
0x34b655…2a6f
4 touches
1 conflict
0xb7a3240c…dd63
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
0xec8551d0…0edd
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity