← previous blocknext block →recent activity
Analyzing
Block #84,362,834
12 transactions · 9 stateful · 2026-06-29 01:11:14 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,362,834 · 12 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
4w05w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ec82b22…1f46
0x34b655…2a6f
4 touches
1 conflict
0xe334a6b5…173c
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x178f9fc2…99a4
0x34b655…2a6f
4 touches
1 conflict
0x398b7303…2c98
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…953a
0x188d58…ea8e
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 0x3ec82b22de…041f46
Audit this contract →
← previous block·next block →recent activity