← previous blocknext block →recent activity
Analyzing
Block #84,307,409
18 transactions · 17 stateful · 2026-06-28 19:01:53 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,307,409 · 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
5w06w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b6e8fc2…73d4
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x27378ed2…65bd
0x3c2269…cf62
2 touches
0 conflicts
0x81d67c49…e69c
0x3c2269…cf62
2 touches
0 conflicts
0x901c81a3…2980
0x3c2269…cf62
2 touches
0 conflicts
0xd2fc21b0…f410
0x3c2269…cf62
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 0x1b6e8fc296…6073d4
Audit this contract →
← previous block·next block →recent activity