← previous blocknext block →recent activity
Analyzing
Block #84,253,538
16 transactions · 15 stateful · 2026-06-28 13:02:52 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,253,538 · 16 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
1w02w15w06w08w19w011w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x89819eca…4891
0x40c49f…2af0
4 touches
1 conflict
0x46d5a052…ff2e
0x34b655…2a6f
4 touches
1 conflict
0x6134a60e…bda6
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
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
1 conflict on slot 0xe2e454194e…59f17b
Audit this contract →
← previous block·next block →recent activity