← previous blocknext block →recent activity
Analyzing
Block #84,365,268
21 transactions · 18 stateful · 2026-06-29 01:27:27 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,365,268 · 21 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
1w02w14w09w110w011w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7534f53d…6ed4
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1564aef8…90c9
0x34b655…2a6f
4 touches
1 conflict
0x64fddb5d…5d3d
0x40c49f…2af0
2 touches
0 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
2 touches
0 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
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 0x7534f53d7a…5a6ed4
Audit this contract →
← previous block·next block →recent activity