← previous blocknext block →recent activity
Analyzing
Block #84,512,736
30 transactions · 26 stateful · 2026-06-29 17:50:42 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,512,736 · 30 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
1w05w16w07w18w29w010w111w214w015w116w017w218w319w420w524w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0x213ee207…a151
0x69df8a…6292
4 touches
1 conflict
0x46279ae7…20dd
0x69df8a…6292
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity