← previous blocknext block →recent activity
Analyzing
Block #84,411,600
15 transactions · 13 stateful · 2026-06-29 06:36:14 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,411,600 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w08w29w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19bfb0e5…73b4
0x34b655…2a6f
4 touches
1 conflict
0x23fe750a…324c
0x34b655…2a6f
4 touches
1 conflict
0x38ec2c24…ef42
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x64029c4a…d430
0x34b655…2a6f
4 touches
1 conflict
0x6e0b4aaf…c32d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0x19bfb0e559…d673b4
Audit this contract →
← previous block·next block →recent activity