← previous blocknext block →recent activity
Analyzing
Block #84,495,841
15 transactions · 13 stateful · 2026-06-29 15:57:56 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,495,841 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w29w310w111w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb6836671…5c3c
0x34b655…2a6f
4 touches
1 conflict
0xc94da5de…7ca7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5df6102c…6494
0xa6afd3…d132
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
3 conflicts on slot 0x742436a7e5…69c4d4
Audit this contract →
← previous block·next block →recent activity