← previous blocknext block →recent activity
Analyzing
Block #83,577,200
11 transactions · 9 stateful · 2026-06-25 09:53:47 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,577,200 · 11 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
1w02w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeed678b1…3103
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1b2c54a1…5a76
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x19c11f2e…80ae
0x065c9d…c394
2 touches
0 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0xe197d213…c62d
0x065c9d…c394
2 touches
0 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
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 0xeed678b1e5…9d3103
Audit this contract →
← previous block·next block →recent activity