← previous blocknext block →recent activity
Analyzing
Block #83,400,837
12 transactions · 12 stateful · 2026-06-24 14:16:52 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,400,837 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24afc70d…36ef
0x34b655…2a6f
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0xb216de79…2b70
0x065c9d…c394
2 touches
0 conflicts
0x0833f1ab…71e7
0x34b655…2a6f
2 touches
0 conflicts
0x275c7ac4…bc94
0x34b655…2a6f
2 touches
0 conflicts
0x8b305a3b…1c35
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: Perpl
1 conflict on slot 0x24afc70d20…6c36ef
Audit this contract →
← previous block·next block →recent activity