← previous blocknext block →recent activity
Analyzing
Block #83,410,307
14 transactions · 13 stateful · 2026-06-24 15:20:10 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,410,307 · 14 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
2w03w14w06w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71632345…6ee9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x0835adb5…ad83
0x34b655…2a6f
3 touches
1 conflict
0x60ee1a20…a8ea
0x065c9d…c394
2 touches
0 conflicts
0x7fe3cfa3…705f
0x065c9d…c394
2 touches
0 conflicts
0xb7267fe5…d586
0x065c9d…c394
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: Perpl
3 conflicts on slot 0x7163234506…a86ee9
Audit this contract →
← previous block·next block →recent activity