← previous blocknext block →recent activity
Analyzing
Block #84,490,926
8 transactions · 7 stateful · 2026-06-29 15:25:07 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,490,926 · 8 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0x370475bf…772c
0x34b655…2a6f
4 touches
1 conflict
0x77e09e77…ea21
0xd32edf…ff58
3 touches
1 conflict
0x0b67b046…7631
0x34b655…2a6f
2 touches
0 conflicts
0x0c5c0224…826e
0x34b655…2a6f
2 touches
0 conflicts
0x39fa7a0d…33a4
0x34b655…2a6f
2 touches
0 conflicts
0x454d8940…cfe7
0x34b655…2a6f
2 touches
0 conflicts
0x67fc285e…2584
0x34b655…2a6f
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 0xda7f9bd20d…e9e332
Audit this contract →
← previous block·next block →recent activity