← previous blocknext block →recent activity
Analyzing
Block #84,352,689
32 transactions · 27 stateful · 2026-06-29 00:03:32 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,352,689 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w18w09w110w011w112w213w314w417w021w223w124w328w029w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x454d8940…cfe7
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
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: 0xd637b38f…c64160
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity