← previous blocknext block →recent activity
Analyzing
Block #83,469,686
13 transactions · 11 stateful · 2026-06-24 21:56:47 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,469,686 · 13 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
7w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89fa3104…8020
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa8d58617…f0d4
0x34b655…2a6f
4 touches
1 conflict
0x1da1c6cb…bb3f
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x56266b4d…5f10
0x34b655…2a6f
4 touches
1 conflict
0x08bf1abb…825d
0x34b655…2a6f
2 touches
0 conflicts
0x101dbdd2…ab8d
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 0x89fa310462…5f8020
Audit this contract →
← previous block·next block →recent activity