← previous blocknext block →recent activity
Analyzing
Block #84,365,260
24 transactions · 20 stateful · 2026-06-29 01:27:23 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,365,260 · 24 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
1w03w04w15w27w08w19w113w214w315w016w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfe63d66…c3e6
0x34b655…2a6f
6 touches
3 conflicts
0x75cdffd8…c217
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x93641233…06f5
0x34b655…2a6f
6 touches
3 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x7d11b6ab…9c3b
0x34b655…2a6f
4 touches
1 conflict
0xb389e502…7af0
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
3 conflicts on slot 0xbfe63d66dd…96c3e6
Audit this contract →
← previous block·next block →recent activity