← previous blocknext block →recent activity
Analyzing
Block #84,543,924
16 transactions · 16 stateful · 2026-06-29 21:18:50 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,543,924 · 16 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
5w06w07w08w110w111w212w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xceb535f3…19cf
0x34b655…2a6f
8 touches
6 conflicts
0xf58f96f0…2f85
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x46664462…acb0
0x34b655…2a6f
6 touches
3 conflicts
0x26918bca…6c75
0x34b655…2a6f
6 touches
3 conflicts
0x6b47245e…a342
0x34b655…2a6f
6 touches
3 conflicts
0x86977b3d…a9c4
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
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 0xceb535f356…6319cf
Audit this contract →
← previous block·next block →recent activity