← previous blocknext block →recent activity
Analyzing
Block #83,642,561
18 transactions · 14 stateful · 2026-06-25 17:10:16 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,642,561 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w08w213w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b61212e…558e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xff4ee2c4…6e5e
0x34b655…2a6f
4 touches
1 conflict
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
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 0x8b61212ee1…d1558e
Audit this contract →
← previous block·next block →recent activity