← previous blocknext block →recent activity
Analyzing
Block #84,516,115
13 transactions · 12 stateful · 2026-06-29 18:13:15 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,516,115 · 13 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
2w03w16w07w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0xcdd7f0a5…d417
0x34b655…2a6f
4 touches
1 conflict
0x0388b940…f9e1
0x34b655…2a6f
2 touches
0 conflicts
0x03d19097…f233
0x34b655…2a6f
2 touches
0 conflicts
0x055a7943…c67a
0x34b655…2a6f
2 touches
0 conflicts
0x408e1b25…3f33
0x34b655…2a6f
2 touches
0 conflicts
0x56b11b75…7881
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity