← previous blocknext block →recent activity
Analyzing
Block #83,671,232
14 transactions · 14 stateful · 2026-06-25 20:21:30 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,671,232 · 14 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
3w04w15w27w011w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913ebf0e…d816
0x34b655…2a6f
8 touches
6 conflicts
0xde696e46…6446
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x582bb904…f513
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
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
6 conflicts on slot 0x913ebf0e0a…d2d816
Audit this contract →
← previous block·next block →recent activity