← previous blocknext block →recent activity
Analyzing
Block #83,197,540
15 transactions · 13 stateful · 2026-06-23 15:38:43 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,197,540 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505f101e…7ad6
0x34b655…2a6f
4 touches
1 conflict
0xb147eeb0…d658
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x31675003…c52f
0x34b655…2a6f
2 touches
0 conflicts
0x59b5f64e…5336
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 0x505f101e7e…6e7ad6
Audit this contract →
← previous block·next block →recent activity