← previous blocknext block →recent activity
Analyzing
Block #84,574,122
16 transactions · 13 stateful · 2026-06-30 00:40:30 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,574,122 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w111w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xb44d5376…33cc
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x4384dd01…4f99
0x34b655…2a6f
4 touches
1 conflict
0x469607a6…3940
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity