← previous blocknext block →recent activity
Analyzing
Block #83,410,642
29 transactions · 26 stateful · 2026-06-24 15:22:25 UTC
Parallelism
76/100
Blocked
58%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,410,642 · 29 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
2w03w14w25w36w07w18w29w311w412w413w514w615w416w527w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x3dbdac49…77f6
0x34b655…2a6f
6 touches
3 conflicts
0x3aac8ffa…ff38
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdcc29079…145d
0x065c9d…c394
6 touches
3 conflicts
0x0835adb5…ad83
0x34b655…2a6f
6 touches
3 conflicts
0x9c7571b3…9605
0x34b655…2a6f
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