← previous blocknext block →recent activity
Analyzing
Block #84,400,279
18 transactions · 17 stateful · 2026-06-29 05:20:52 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,400,279 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d35c08d…3abc
0x34b655…2a6f
4 touches
1 conflict
0x8a7af3fd…72a6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x21fb22cb…fcd2
0x34b655…2a6f
3 touches
1 conflict
0x40cd0940…ff35
0x34b655…2a6f
2 touches
0 conflicts
0x75194ada…a1c5
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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 0x6d35c08d4a…063abc
Audit this contract →
← previous block·next block →recent activity