← previous blocknext block →recent activity
Analyzing
Block #84,029,665
12 transactions · 10 stateful · 2026-06-27 12:11:50 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,029,665 · 12 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
1w04w18w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc9fe0433…7f01
0x34b655…2a6f
7 touches
6 conflicts
0x73ca2093…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x6a0d9e84…2b0b
0x34b655…2a6f
4 touches
1 conflict
0x6c1baaf7…c0a0
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity