← previous blocknext block →recent activity
Analyzing
Block #83,671,225
12 transactions · 11 stateful · 2026-06-25 20:21:27 UTC
Parallelism
42/100
Blocked
55%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,671,225 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913ebf0e…d816
0x34b655…2a6f
10 touches
10 conflicts
0x68c6b2fa…098d
0x34b655…2a6f
8 touches
6 conflicts
0x1274880c…3cdc
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x86977b3d…a9c4
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
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
10 conflicts on slot 0x913ebf0e0a…d2d816
Audit this contract →
← previous block·next block →recent activity