← previous blocknext block →recent activity
Analyzing
Block #83,210,876
8 transactions · 6 stateful · 2026-06-23 17:07:57 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,210,876 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0x369a11e2…566f
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xefb14ec3…ce7c
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x7ec6cf94…2ba7
0x34b655…2a6f
2 touches
0 conflicts
0x8579b76e…18da
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 0xb9b4eff6b7…8cc3ef
Audit this contract →
← previous block·next block →recent activity