← previous blocknext block →recent activity
Analyzing
Block #84,426,115
10 transactions · 9 stateful · 2026-06-29 08:12:56 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,426,115 · 10 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
5w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x158cd556…852d
0x34b655…2a6f
2 touches
0 conflicts
0x19bfb0e5…73b4
0x34b655…2a6f
2 touches
0 conflicts
0x2ea9c952…a31e
0x34b655…2a6f
2 touches
0 conflicts
0x38713b17…3b8e
0x34b655…2a6f
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 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity