← previous blocknext block →recent activity
Analyzing
Block #84,357,040
23 transactions · 16 stateful · 2026-06-29 00:32:34 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,357,040 · 23 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
1w04w05w19w010w011w114w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1b0fcc8c…1a03
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xf43088bc…e9e1
0x065c9d…c394
3 touches
1 conflict
0x3e9dcba8…4eca
0xd32edf…ff58
3 touches
1 conflict
0xc5172627…9da0
0x065c9d…c394
3 touches
1 conflict
0x213ee207…a151
0x69df8a…6292
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: 0x681e908b…e1ae09
1 conflict on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity