← previous blocknext block →recent activity
Analyzing
Block #84,494,133
35 transactions · 26 stateful · 2026-06-29 15:46:32 UTC
Parallelism
80/100
Blocked
69%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,494,133 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w310w411w412w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x9af72ba2…f151
0x34b655…2a6f
10 touches
10 conflicts
0xbc9aaf19…8cfd
0x34b655…2a6f
10 touches
10 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity