← previous blocknext block →recent activity
Analyzing
Block #83,630,810
14 transactions · 8 stateful · 2026-06-25 15:51:44 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,630,810 · 14 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
1w08w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fde64da…aa3e
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1f328966…f4d5
0x851145…3f07
4 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x0fde64da0b…a5aa3e
Audit this contract →
← previous block·next block →recent activity