← previous blocknext block →recent activity
Analyzing
Block #83,203,410
10 transactions · 7 stateful · 2026-06-23 16:17:59 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,203,410 · 10 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
3w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3817764d…242b
0x34b655…2a6f
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xb25f119b…cd99
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x2ea84399…5bad
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
3 conflicts on slot 0x3817764d6e…67242b
Audit this contract →
← previous block·next block →recent activity