← previous blocknext block →recent activity
Analyzing
Block #83,655,418
10 transactions · 10 stateful · 2026-06-25 18:36:03 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,655,418 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0xa0c6e179…a103
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2e461bf0…9a56
0x065c9d…c394
2 touches
0 conflicts
0x4388045a…c325
0x065c9d…c394
2 touches
0 conflicts
0x4f11ee85…c9a5
0x065c9d…c394
2 touches
0 conflicts
0xc1e0fdac…a7a8
0x065c9d…c394
2 touches
0 conflicts
0xfd03e05a…ba0b
0x065c9d…c394
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 0x2c53a187ea…bc3646
Audit this contract →
← previous block·next block →recent activity