← previous blocknext block →recent activity
Analyzing
Block #83,455,830
16 transactions · 12 stateful · 2026-06-24 20:24:15 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,455,830 · 16 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
6w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505f101e…7ad6
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2f7f1a44…eeeb
0x34b655…2a6f
4 touches
1 conflict
0x95cb8e34…5eba
0x34b655…2a6f
4 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0xe5bb3628…e5e8
0x34b655…2a6f
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
2 touches
0 conflicts
0x2e3402ad…e443
0x754704…b603
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
3 conflicts on slot 0x505f101e7e…6e7ad6
Audit this contract →
← previous block·next block →recent activity