← previous blocknext block →recent activity
Analyzing
Block #83,668,870
18 transactions · 13 stateful · 2026-06-25 20:05:45 UTC
Parallelism
89/100
Blocked
15%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,668,870 · 18 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
4w06w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913ebf0e…d816
0x34b655…2a6f
4 touches
1 conflict
0xd2c5964e…c17b
0x34b655…2a6f
4 touches
1 conflict
0xde696e46…6446
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x280117c9…f4b6
0x34b655…2a6f
2 touches
0 conflicts
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x582bb904…f513
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
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 0x913ebf0e0a…d2d816
Audit this contract →
← previous block·next block →recent activity