← previous blocknext block →recent activity
Analyzing
Block #83,691,830
10 transactions · 10 stateful · 2026-06-25 22:38:54 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,691,830 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x00966e54…7d1d
0x34b655…2a6f
2 touches
0 conflicts
0x0ad4dbe8…ae93
0x34b655…2a6f
2 touches
0 conflicts
0x2a0a67ca…d37d
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
1 conflict on slot 0xdc8d4ee099…56def3
Audit this contract →
← previous block·next block →recent activity