← previous blocknext block →recent activity
Analyzing
Block #83,035,052
10 transactions · 7 stateful · 2026-06-22 21:32:03 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,035,052 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x7bc74ef3…0fee
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0019224b…ad0f
0x34b655…2a6f
2 touches
0 conflicts
0x1436b7d8…a80b
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
2 touches
0 conflicts
0x8c5c7e52…01b8
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 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity