← previous blocknext block →recent activity
Analyzing
Block #83,942,152
21 transactions · 14 stateful · 2026-06-27 02:28:42 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,942,152 · 21 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
1w04w05w17w210w115w116w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x189b3d65…b7da
0x065c9d…c394
3 touches
1 conflict
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0xac2a0273…7212
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: 0xd637b38f…c64160
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity